Loading vulnerability…
A stack-based buffer overflow exists in the IMAP daemon (imapd) of MailEnable Professional versions prior to 1.6 and Enterprise Edition prior to 1.1. The vulnerability is triggered when an authenticated user issues a STATUS command with an excessively long mailbox name, causing a buffer overflow that can be leveraged to execute arbitrary code with the privileges of the imapd 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.
This repository contains a single Metasploit module (modules/exploits/windows/imap/mailenable_status.rb) that exploits a buffer overflow vulnerability (CVE-2005-2278) in the STATUS command of MailEnable IMAPD version 1.54. The exploit requires valid IMAP credentials and targets the IMAP service over the network (typically port 143/tcp). The module constructs a specially crafted STATUS request with a long buffer and a custom SEH payload, allowing for arbitrary code execution on the target system. The exploit supports multiple Windows platforms and is fully integrated into the Metasploit framework, allowing for customizable payloads. The code is mature and weaponized, providing reliable exploitation capabilities for penetration testers.
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.