Threats / Microsoft / CVE-2017-0147
CVE-2017-0147
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Microsoft SMBv1 server vulnerability
SMBv1 server in Microsoft Windows allows remote attackers to obtain sensitive information from process memory via crafted packets, enabling information disclosure attacks.
Verdict
Today item, not a backlog item.
This vulnerability permits unauthenticated remote memory disclosure through SMBv1, facilitating reconnaissance and credential harvesting. Active exploitation in ransomware campaigns demonstrates severe real-world impact and operational risk.
CISA KEV Yes · 2022-05-244Ransomware use Flagged4EPSS 0.99693 (verify live)5CVSS 7.5 (CISA)3CISA SSVC Exploitation: active · Automatable: yes · Impact: partial3Exploit Weaponized · public exploit · Metasploit module11
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
26 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-05-24), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.99693 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) · Affected: Microsoft, SMBv1 server. 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-200 Information Exposure — weakness family: Authorization / access control.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: yes · Technical Impact: partialCISA'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 1894 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 packet to trigger memory disclosure from the target Windows system.
Business
Sensitive data including credentials and system information is exposed to the attacker without authentication.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I extract credentials and system details from the disclosed memory to establish persistence or lateral movement.
Business
Compromised credentials enable attackers to escalate privileges and move through the network infrastructure.
3
Lateral reach — past segmentation narrative 3
Attacker
I deploy ransomware or additional payloads using the obtained access and information.
Business
Systems are encrypted or compromised, resulting in operational downtime, data loss, and financial extortion demands.
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