Threats / Microsoft / CVE-2017-0144
CVE-2017-0144
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Microsoft SMBv1 vulnerability
SMBv1 server in Microsoft Windows accepts crafted packets leading to remote code execution. Actively exploited in ransomware campaigns.
Verdict
Today item, not a backlog item.
Critical remote code execution vulnerability in SMBv1 affecting multiple Windows versions. Unauthenticated attackers can execute arbitrary code over the network. Widespread exploitation documented in ransomware operations.
CISA KEV Yes · 2022-02-104Ransomware use Flagged4EPSS 0.9923 (verify live)5Exploit Weaponized · public PoC6CVSS 8.8 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
74 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-02-10), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.9923 — 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, SMBv1. 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 1791 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 malicious SMB packets targeting unpatched Windows SMBv1 implementations to achieve network access without authentication.
Business
Attackers gain initial foothold across enterprise networks, bypassing perimeter controls and establishing persistence.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute arbitrary code with system privileges on compromised hosts to install ransomware payloads or establish command infrastructure.
Business
Ransomware operators encrypt critical business data and systems, demanding payment while operations cease and data breach risks materialize.
3
Lateral reach — past segmentation narrative 3
Attacker
I propagate laterally across the network using compromised credentials and SMBv1 vulnerabilities to maximize encryption scope.
Business
Entire network segments become unavailable; recovery costs, ransom demands, and regulatory fines accumulate across the organization.
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