basicsecurity.net
Proof, not just disclosure.
Threats / Microsoft / CVE-2017-0146
CVE-2017-0146 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

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-253Ransomware use Flagged3EPSS 0.89862 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported 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.
CISA KEV ↗Confirmed
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
Affected: Microsoft, Windows. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-20 Improper Input Validation.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • Ransomware-use flag (CISA)
  • EPSS probability (FIRST)
  • 12 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by microsoft (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by microsoftCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.