Loading vulnerability…
A stack-based buffer overflow exists in the Microsoft Message Queuing (MSMQ) service on Microsoft Windows 2000 Server SP4, Windows 2000 Professional SP4, and Windows XP SP2. The vulnerability is triggered by sending a specially crafted long string in an opnum 0x06 RPC call to port 2103. This allows remote attackers to execute arbitrary code on the affected system. The vulnerability is remotely exploitable, particularly on Windows 2000 Server.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (3 hidden).
This repository contains a single Metasploit exploit module targeting the Microsoft Message Queueing (MSMQ) service stack buffer overflow vulnerability (CVE-2007-3039, MS07-065) on Windows 2000 Server. The exploit abuses the DCERPC interface (UUID fdb3a030-065f-11d1-bb9b-00a024ea5525) over TCP port 2103. It requires the attacker to supply the fully-qualified DNS hostname (FQDN) of the target as configured in Windows, which is used to craft a malicious buffer that triggers the overflow. The module allows for customizable payloads (up to 1024 bytes, avoiding certain bad characters) and, if successful, results in remote code execution as SYSTEM. The code is written in Ruby and is structured as a standard Metasploit module, with options for the target port and DNS name. No hardcoded IPs or URLs are present, but the exploit is fingerprintable by its use of the MSMQ DCERPC UUID and port 2103.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.