CVE-2017-0145 is a remote code execution vulnerability in the SMBv1 server implementation in multiple Microsoft Windows versions, including Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 and 2012 R2, Windows RT 8.1, Windows 10 Gold/1511/1607, and Windows Server 2016. The flaw can be triggered by sending specially crafted packets to a reachable SMBv1 service. Successful exploitation allows arbitrary code execution on the target system. The vulnerability was addressed by Microsoft in MS17-010 and became widely known through use in EternalBlue-enabled wormable attacks such as WannaCry.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
3 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (4 hidden).
This repository is a small lab/demo project built around a Metasploit exploit module and a harmless ransomware-themed batch script. Because it is part of the Metasploit framework, the main exploit file is ms17_010_eternalblue.rb, a Ruby Metasploit module implementing the EternalBlue SMB exploit against vulnerable Microsoft Windows SMBv1 targets. The module is clearly a real exploit, not just a detector: it performs SMB protocol interaction over TCP/445, supports anonymous or credentialed SMB authentication, uses the auxiliary/scanner/smb/smb_ms17_010 check module, and is designed to achieve remote kernel memory corruption leading to arbitrary code execution. The module metadata indicates support for multiple Windows versions including Windows 7, Windows Embedded Standard 7, Server 2008 R2, Windows 8/8.1, Server 2012, and some Windows 10 Pro builds, and references the MS17-010 vulnerability set (CVE-2017-0143 through CVE-2017-0148). In practical use, the README demonstrates pairing it with a windows/x64/meterpreter/reverse_tcp payload to obtain a SYSTEM-level Meterpreter session. Repository structure is simple: README.md documents a university lab exercise, exploitation workflow, post-exploitation commands, and mitigation via KB4012212; ms17_010_eternalblue.rb is the actual exploit module; wannacry64.bat is a separate Windows batch file that only simulates a WannaCry-style ransom screen. The batch file contains no encryption, persistence, propagation, or destructive logic; it displays a countdown, fake progress bar, sample filenames, and a hardcoded Bitcoin address as part of the visual demo. Overall, the repository’s purpose is educational: demonstrate exploitation of MS17-010 in an isolated lab, show post-exploitation access, and then illustrate a safe ransomware-themed payload simulation plus patch-based mitigation.
This repository contains a single Metasploit module implementing the 'EternalBlue' exploit (MS17-010) targeting the SMBv1 service on various versions of Microsoft Windows. The exploit leverages a buffer overflow vulnerability in the Windows SMB kernel driver, allowing remote code execution as SYSTEM. The module is highly weaponized, supporting customizable payloads and targeting a wide range of Windows operating systems (Windows 7, 8, 8.1, 10 Pro, Server 2008 R2, Server 2012, and Embedded Standard 7). The exploit operates over the network, requiring access to TCP port 445 on the target. The code is written in Ruby and is designed to be used within the Metasploit framework, providing a user-friendly interface for payload selection and exploitation. No hardcoded IPs or domains are present; the target is specified by the user at runtime. The module also supports both anonymous and credentialed SMB sessions, increasing its flexibility and effectiveness.
This repository contains a single Metasploit module: 'SMB DOUBLEPULSAR Remote Code Execution' (smb_doublepulsar_rce.rb). The module targets Windows systems that have been compromised with the DOUBLEPULSAR SMB implant, which is often deployed via the ETERNALBLUE exploit (MS17-010). The exploit allows an attacker to execute arbitrary Metasploit payloads (such as Meterpreter reverse shells) on the infected system by communicating with the DOUBLEPULSAR backdoor over SMB (port 445). The module also provides an option to neutralize (disable) the implant. The main endpoints involved are the SMB IPC$ share on the target and the process (default: spoolsv.exe) into which the payload is injected. The code is written in Ruby and is fully integrated into the Metasploit framework, making it a weaponized and highly customizable exploit. The module references multiple CVEs related to MS17-010 and is suitable for post-exploitation scenarios where DOUBLEPULSAR is already present on the target.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Windows SMBv1 remote code execution vulnerability (part of the MS17-010 set) referenced as heavily exploited and associated with ransomware outbreaks.
A critical SMB vulnerability in Microsoft Windows (EternalBlue) exploited for remote code execution, widely used in ransomware and malware campaigns.
A Windows SMB vulnerability used by the leaked EternalBlue exploit to enable wormable propagation in WannaCry.
A Microsoft Windows SMB remote code execution vulnerability referenced as part of IPS protections and likely among the outdated exploits used for self-spreading.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.