CVE-2017-0144: EternalBlue
Is CVE-2017-0144 real, exploitable, or a false positive? Here's the community verdict.
Community verdict: No field verdicts yet. Be the first practitioner to weigh in.
signals
public sources
Confirmed exploited in the wild. Patch this first, regardless of the base score.
cisa ssvc
CISA Vulnrichment · assessed
CISA decision, by how critical the affected system is to you:
- low impact → Track
- medium impact → Attend
- high impact → Act
Track: normal patch cycle · Track*: watch closely · Attend: patch sooner · Act: patch now. About SSVC ↗
public exploits
links to sources — we don’t host codeA working exploit is publicly available from a maintained source. Treat this as higher urgency and verify your exposure.
baseline read
auto · not a community verdict
Real — exploited in the wild
CISA confirms active exploitation. Treat scanner hits as true positives unless your specific version or config is unaffected.
Based on CISA KEV
Confirm or dispute →CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows Server 2012 Gold and R2; Windows RT 8.1; and Windows 10 Gold, 1511, and 1607; and Windows Server 2016 allows remote attackers to execute arbitrary code via crafted packets, aka "Windows SMB Remote Code Execution Vulnerability." This vulnerability is different from those described in CVE-2017-0143, CVE-2017-0145, CVE-2017-0146, and CVE-2017-0148.
References
Published · Added to CISA KEV (1791 days after publication)
Embed this verdict
[](https://www.truepositive.app/cve/CVE-2017-0144)<a href="https://www.truepositive.app/cve/CVE-2017-0144"><img src="https://www.truepositive.app/cve/CVE-2017-0144/badge.svg" alt="TruePositive verdict for CVE-2017-0144"></a>Live badge that updates automatically as the community verdict changes.
timeline
- CISA SSVC assessment · exploitation: active
- Added to CISA KEV · confirmed exploited in the wild
- Published by NVD
- Added to VulnCheck KEV · reported exploited in the wild
Score and exploit changes tracked since .
Community ground truth
Be the first practitioner to weigh in
So far this is only TruePositive's editorial baseline from public sources. Add your real-world verdict below — it becomes the signal the next person triaging this relies on.
🥇 The first 50 practitioners to contribute earn a Founding Contributor badge.
In your experience, is this finding real and exploitable?
awaiting field verdictsCurated baseline: TruePositive's read from public sources is Real & exploitable — a starting point, not a community verdict.
No account needed. Anonymous verdicts post as an unverified signal. Log in to make yours verified and earn reputation.
Field notes & remediation
Verdicts are the quick signal. Notes are the evidence and fixes behind them.
- 0
This is one of the most damaging bugs ever. It powered WannaCry and NotPetya. It is a flaw in Windows SMBv1 (file sharing). An attacker on the network can run code on an unpatched Windows machine with no login, and it spreads on its own like a worm. If SMBv1 is exposed and the machine is unpatched, it is game over.
Who is affected: unpatched Windows versions (from XP up to the Server 2016 era) that still have SMBv1 enabled and reachable. Microsoft fixed it in MS17-010 (March 2017), and even shipped an emergency patch for end-of-life Windows XP because it was that serious.
To check: confirm the MS17-010 patch is installed, and check whether SMBv1 is enabled and exposed. A ready-made check exists (
auxiliary/scanner/smb/smb_ms17_010). If SMBv1 is exposed on an unpatched box, assume it is exploitable and possibly already compromised.Commonly flagged by: Nessus, Qualys, OpenVAS, Rapid7.
- 0
Install the MS17-010 patch. More importantly, disable SMBv1 completely everywhere. It is a dead protocol and should not be running today. Block SMB (ports 445 and 139) at the network edge so it is never reachable from the internet. If a machine was exposed and unpatched, treat it as compromised and investigate.