Loading vulnerability…
Multiple stack-based buffer overflows exist in the IMAP service of Mercury/32 version 4.01a. These vulnerabilities are triggered by sending excessively long arguments to various IMAP commands (including EXAMINE, SUBSCRIBE, STATUS, APPEND, CHECK, CLOSE, EXPUNGE, FETCH, RENAME, DELETE, LIST, SEARCH, CREATE, and UNSUBSCRIBE) after authenticating to the service. Exploitation allows remote authenticated attackers to crash the service or potentially execute arbitrary code with the privileges of the Mercury/32 process.
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 (6 hidden).
This repository contains a single Metasploit module (mercury_rename.rb) that exploits a stack buffer overflow vulnerability (CVE-2004-1211) in the Mercury/32 v4.01a IMAP service. The exploit targets Windows 2000 SP4 and Windows XP Pro (SP0/SP1) systems running the vulnerable IMAP service. The module connects to the IMAP service over the network and sends a specially crafted RENAME command with an overly long argument, causing a buffer overflow and allowing execution of arbitrary code. The payload is fully customizable using Metasploit's payload system, supporting a variety of post-exploitation actions. The module includes a check method to verify if the target is running the vulnerable version. The only fingerprintable endpoint is the IMAP service (typically on TCP port 143) of the target host. The code is written in Ruby and is structured as a standard Metasploit exploit module.
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.