A stack-based buffer overflow exists in Qualcomm WorldMail 3.0's IMAP service. The vulnerability is triggered when a remote attacker sends an overly long IMAP command ending with a '}' character. Specifically, commands such as LIST, LSUB, SEARCH TEXT, STATUS INBOX, AUTHENTICATE, FETCH, SELECT, and COPY are affected. The overflow occurs due to insufficient bounds checking when copying user-supplied data to a stack buffer, allowing for the execution of arbitrary code.
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 (modules/exploits/windows/imap/eudora_list.rb) that exploits a stack buffer overflow vulnerability (CVE-2005-4267) in the Qualcomm WorldMail 3.0 IMAP Server (builds 6.1.19.0 through 6.1.22.0) on Windows. The exploit works by sending a specially crafted IMAP LIST command containing a payload and SEH overwrite, allowing arbitrary code execution. The module includes automatic target version detection based on the IMAP server banner and supports multiple specific builds. The payload is customizable via Metasploit and can be up to 750 bytes. The attack vector is network-based, targeting the IMAP service (typically port 143/tcp). The exploit is operational and can be used to gain remote code execution on vulnerable systems. The repository is structured as a standard Metasploit exploit module, written in Ruby, and is intended for use within the Metasploit Framework.
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.