Loading vulnerability…
A buffer overflow vulnerability exists in the Message Queuing component of Microsoft Windows 2000 and Windows XP SP1. The flaw allows remote attackers to send a specially crafted message to the Message Queuing service, resulting in a buffer overflow condition. This can lead to the execution of arbitrary code with the privileges of the Message Queuing service.
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 (1 hidden).
This repository contains a single Metasploit module (ms05_017_msmq.rb) that exploits a stack buffer overflow vulnerability (CVE-2005-0059) in the Microsoft Message Queueing (MSMQ) service on Windows 2000 and Windows XP SP0-SP1 (English). The exploit targets the DCERPC interface of MSMQ, specifically on TCP port 2103, and requires the NetBIOS hostname of the target to reliably calculate the buffer offset. The module allows the attacker to execute arbitrary code with SYSTEM privileges by sending a specially crafted queue path to the vulnerable service. The payload is customizable via the Metasploit framework, supporting various post-exploitation actions. The code is written in Ruby and is structured as a standard Metasploit exploit module, with options for target selection, payload configuration, and automatic handling of network connections. No hardcoded IP addresses or domain names 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.