Loading vulnerability…
A buffer overflow vulnerability exists in Mercury Mail Transport System version 4.01b. The flaw is triggered when a remote attacker sends a specially crafted long request to TCP port 105, resulting in a buffer overflow condition. This can allow the attacker to overwrite memory and potentially execute arbitrary code on the affected system.
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 exploit module targeting a stack-based buffer overflow vulnerability in the Mercury/32 PH Server Module (CVE-2005-4411). The exploit is designed for Windows XP Pro SP0/SP1 English and Windows 2000 Pro English systems running Mercury/32 PH Server version 4.01b or earlier. The vulnerability is triggered by sending a specially crafted payload to TCP port 105, which overflows a fixed-size buffer and allows for arbitrary code execution. The module supports customizable payloads up to 500 bytes, avoiding specific bad characters, and leverages Metasploit's handler for post-exploitation. The code is written in Ruby and follows the standard Metasploit module structure, making it easy to use within the framework. No hardcoded IP addresses or URLs are present; the only fingerprintable endpoint is the default TCP port 105 used by the PH server.
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.