Vulnerability in capstone (CVE-2017-6952)
Summary
Vulnerability in capstone (CVE-2017-6952). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 6fe86eef621b9849f51a5e1e5d73258a93440403, 3.0.5rc2 or later.
Original description
The description as published by the source.
Integer overflow in the cs_winkernel_malloc function in winkernel_mm.c in Capstone 3.0.4 and earlier allows attackers to cause a denial of service (heap-based buffer overflow in a kernel driver) or possibly have unspecified other impact via a large value.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2017-6952 has been found in capstone.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade capstone to 6fe86eef621b9849f51a5e1e5d73258a93440403, 3.0.5rc2 or later.
If unsure, ask your IT team or search "capstone CVE-2017-6952" on the vendor's site.
CVE-2017-6952 (capstone) — CWE-190 / CVSS v3 8.8
Attack vector: remote (network-reachable) / unauthenticated
Patched: 6fe86eef621b9849f51a5e1e5d73258a93440403, 3.0.5rc2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-190) exists in capstone.
Check the vendor advisory for the affected versions of capstone.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 6fe86eef621b9849f51a5e1e5d73258a93440403, 3.0.5rc2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'capstone' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'capstone' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
capstoneを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade capstone to 6fe86eef621b9849f51a5e1e5d73258a93440403, 3.0.5rc2ステージング環境で 6fe86eef621b9849f51a5e1e5d73258a93440403, 3.0.5rc2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- patch github.com
- web securityfocus.com