Loading vulnerability…
A stack-based buffer overflow exists in Mercury/32 (Mercury Mail Transport System) version 4.01b and earlier. The vulnerability is triggered by sending an overly long LOGIN command to the service, which can overwrite stack memory and potentially allow for arbitrary code execution.
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 (2 hidden).
This repository contains a single Metasploit module (modules/exploits/windows/imap/mercury_login.rb) that exploits a stack buffer overflow vulnerability in Mercury/32 IMAPD versions 4.01a and 4.01b (CVE-2007-1373). The exploit targets the IMAP LOGIN command by sending a specially crafted payload to TCP port 143, resulting in code execution via SEH overwrite and egghunter techniques. The module is operational and allows the attacker to execute arbitrary shellcode on the target Windows system. The exploit is customizable through Metasploit's payload system, enabling various post-exploitation actions. The code is well-structured, following Metasploit conventions, and includes checks to verify the target version before exploitation. No hardcoded IPs, domains, or file paths are present; the main fingerprintable endpoint is the IMAP service on TCP port 143.
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.