[KEV] Vulnerability in Microsoft SMBv1 (CVE-2017-0144)
Summary
Vulnerability in Microsoft SMBv1 (CVE-2017-0144). Successful exploitation can lead to full system takeover. Listed in CISA KEV — actively exploited.
Original description
The description as published by the source.
The SMBv1 server in multiple Microsoft Windows versions allows remote attackers to execute arbitrary code via crafted packets.
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-0144 has been found in Microsoft SMBv1.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
Note: CISA has officially confirmed this is actively exploited in the wild. Treat it with elevated urgency.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Microsoft SMBv1 CVE-2017-0144" on the vendor's site.
CVE-2017-0144 (Microsoft SMBv1) — CWE-20 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Listed in CISA KEV — actively exploited, treat as top priority.
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-20) exists in Microsoft SMBv1.
Check the vendor advisory for the affected versions of Microsoft SMBv1.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover. Listed in CISA KEV — actively exploited in the wild, treat as top priority.
Update to the patched release per vendor advisory.
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 'SMBv1' . 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 'SMBv1' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
SMBv1を grep し、稼働しているサービス・バージョンを把握する。 -
2Consider incident declaration escalate
Notify SOC / on-callCISA KEV登録済 = 実環境で悪用が観測されている。侵入の兆候があればインシデント対応宣言、無くてもパッチ適用までWAF強化を最優先で。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory NVD
- advisory securityfocus.com
- advisory securitytracker.com
- advisory cert-portal.siemens.com
- advisory cert-portal.siemens.com
- advisory ics-cert.us-cert.gov
- exploit packetstormsecurity.com
- exploit packetstormsecurity.com
- exploit exploit-db.com
- exploit exploit-db.com
- exploit exploit-db.com
- exploit exploit-db.com
- patch portal.msrc.microsoft.com
- web cisa.gov