Threats / Microsoft / CVE-2017-0146
CVE-2017-0146
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Microsoft Windows vulnerability
SMBv1 server in Microsoft Windows allows remote code execution through improper input validation, enabling unauthenticated attackers to execute arbitrary code.
Verdict
Today item, not a backlog item.
Critical remote code execution vulnerability in SMBv1 affecting Windows systems. High EPSS score and confirmed exploitation in ransomware campaigns indicate active threat. Immediate patching required for all affected Windows versions.
CISA KEV Yes · 2022-03-254Ransomware use Flagged4EPSS 0.89862 (verify live)5CVSS 8.8 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3Exploit Weaponized · public exploit · Metasploit module11
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
12 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-03-25), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.89862 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.8 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) · Affected: Microsoft, Windows. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-20 Improper Input Validation.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1834 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious SMBv1 network packet with improper input to trigger code execution on the target Windows system.
Business
Attackers gain initial system compromise without authentication, enabling lateral movement and data exfiltration.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute arbitrary code with system privileges to install ransomware or establish persistent backdoor access.
Business
Ransomware deployment encrypts critical business data and systems, forcing costly recovery operations and potential ransom payments.
3
Lateral reach — past segmentation narrative 3
Attacker
I propagate the exploit across the network to compromise additional Windows hosts at scale.
Business
Widespread infrastructure compromise disrupts operations, damages reputation, and incurs significant incident response and remediation costs.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05