Skip to main content
Mallory
HighCISA KEVExploited in the wildPublic exploit

EternalChampion (Race Condition in SMBv1)

IdentifiersCVE-2017-0146CWE-362

CVE-2017-0146 is a critical race condition vulnerability in the SMBv1 server implementation in multiple versions of Microsoft Windows, including Vista SP2, Windows 7 SP1, Windows 8.1, Windows 10 (Gold, 1511, 1607), Windows Server 2008 SP2/R2 SP1, Windows Server 2012 Gold/R2, Windows Server 2016, and Windows RT 8.1. The vulnerability exists in the way SMB Transaction requests are handled, allowing an unauthenticated remote attacker to exploit a race condition to leak memory and execute arbitrary code on the target system. This vulnerability was exploited by the EternalChampion tool, part of the leaked NSA toolset, and is distinct from other SMBv1 vulnerabilities such as EternalBlue (CVE-2017-0144).

Share:
For your environment

Are you exposed to this one?

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.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote, unauthenticated attackers to execute arbitrary code with system privileges, potentially leading to full system compromise. The vulnerability can be leveraged to leak sensitive memory contents and bypass security boundaries, enabling further lateral movement and privilege escalation within a network. It was a key component in high-profile attacks and malware campaigns, including those that leveraged the EternalChampion exploit.

Mitigation

If you can’t patch tonight, do this now.

As an immediate mitigation, disable the SMBv1 protocol on all Windows systems, as it is not required for modern environments and is a significant attack surface. In addition, restrict access to SMB services at the network perimeter using firewalls or network segmentation. Upgrade to newer Windows versions where SMBv1 is disabled by default and additional kernel mitigations (ASLR, NX, CFG) are present.

Remediation

Patch, then assume compromise.

Apply the security updates provided in Microsoft Security Bulletin MS17-010, which comprehensively address this and related SMBv1 vulnerabilities. The update corrects the handling of SMB Transaction requests to eliminate the race condition. Ensure all affected Windows systems are fully patched.
PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (2 hidden).

VALID 1 / 3 TOTALView more in app
EternalBlue-Exploit-DemonstrationMaturityPoCFrameworkmetasploitVerified exploit

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.

dannic145Disclosed Apr 22, 2026markdownrubynetworkfile
EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationServer Message Blockapplication
SiemensAcuson P300 Firmwareoperating_system
SiemensAcuson P500 Firmwareoperating_system
SiemensAcuson Sc2000 Firmwareoperating_system
SiemensAcuson X700 Firmwareoperating_system
SiemensSyngo Sc2000 Firmwareoperating_system
SiemensTissue Preparation System Firmwareoperating_system
SiemensVersant Kpcr Molecular System Firmwareoperating_system
SiemensVersant Kpcr Sample Prep Firmwareoperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware2

Malware families riding this exploit, with evidence and IOCs.

Detection signatures2

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity

Community discussion across Reddit, Mastodon, and other social sources.