EternalBlue
CVE-2017-0144 is a remote code execution vulnerability in the Microsoft Windows SMBv1 server, exploited by EternalBlue. Improper handling of specially crafted SMBv1 requests allows an unauthenticated remote attacker to execute arbitrary code on an affected system without user interaction. Affected releases include Windows Vista SP2; Windows 7 SP1; Windows 8.1 and RT 8.1; Windows 10 initial release, 1511, and 1607; Windows Server 2008 SP2 and 2008 R2 SP1; Windows Server 2012 and 2012 R2; and Windows Server 2016, including applicable Server Core installations. Microsoft addressed the vulnerability in MS17-010 on March 14, 2017. Exploitation has enabled worm-like propagation and payload deployment by threats including WannaCry and NotPetya.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation permits unauthenticated remote code execution with elevated access, compromising system confidentiality, integrity, and availability. Attackers can deploy malware, access or modify data, and use compromised hosts to attack additional reachable systems. The vulnerability has supported large-scale ransomware and destructive-malware propagation, resulting in data encryption or loss, unavailable systems, and substantial operational disruption. Medical systems running affected Windows components may also experience disruption to clinical services.
If you can’t patch tonight, do this now.
Disable SMBv1 where feasible and use SMBv2 or SMBv3 after compatibility testing. Block Internet-facing SMB and restrict TCP ports 445 and 139 to necessary, trusted systems. Segment or isolate unpatchable hosts and prevent unnecessary workstation-to-workstation SMB access. Deploy IDS/IPS detection for EternalBlue exploitation and immediately isolate compromised systems. Maintain tested offline or immutable backups to limit downstream malware damage. For medical devices, assess clinical and patient-safety implications before disabling protocols or disconnecting equipment.
Patch, then assume compromise.
Apply the operating-system-specific MS17-010 security update or a superseding cumulative update. Original updates include KB4012598 for Windows Vista SP2 and Server 2008 SP2; KB4012212 or KB4012215 for Windows 7 SP1 and Server 2008 R2 SP1; KB4012213 or KB4012216 for Windows 8.1 and Server 2012 R2; KB4012214 or KB4012217 for Server 2012; KB4012216 for Windows RT 8.1; KB4012606 for the initial Windows 10 release; KB4013198 for Windows 10 1511; and KB4013429 for Windows 10 1607 and Server 2016. For embedded medical systems, obtain and install vendor-approved product-specific fixes through the relevant support channel. Verify patch installation across affected assets.
6 exploits validated by Mallory's analysis. Hidden: 28 rejected by Mallory's analysis as not a working exploit; 7 not yet analyzed, such as Exploit-DB entries.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
71 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.