Threats / Microsoft / CVE-2017-0148
CVE-2017-0148
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Microsoft SMBv1 server vulnerability
SMBv1 server in Microsoft products allows remote attackers to execute arbitrary code via crafted packets. This vulnerability has been actively exploited in the wild and leveraged in ransomware campaigns.
Verdict
Today item, not a backlog item.
Critical remote code execution vulnerability in SMBv1 with high real-world exploitation activity. The vulnerability enables unauthenticated attackers to achieve code execution on affected systems, facilitating widespread ransomware deployment and data compromise.
CISA KEV Yes · 2022-04-064Ransomware use Flagged4EPSS 0.99373 (verify live)5Exploit Public PoC6CVSS 8.1 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
9 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-04-06), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.99373 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.1 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) · 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-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 1846 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 SMBv1 packets to trigger memory corruption on the target server.
Business
Attackers gain remote code execution capability without authentication, enabling rapid lateral movement across enterprise networks.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute arbitrary code with system privileges on the compromised host.
Business
Complete system compromise allows deployment of ransomware, data exfiltration, and persistence mechanisms across the organization.
3
Lateral reach — past segmentation narrative 3
Attacker
I propagate the exploit to other systems sharing network access to SMBv1 services.
Business
Widespread infection across infrastructure leads to operational shutdown, financial extortion, and regulatory compliance violations.
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