Loading vulnerability…
A stack-based buffer overflow exists in the IMAP service of MailEnable Professional and Enterprise Editions (versions 2.0 through 2.35, Professional 1.6 through 1.84, and Enterprise 1.1 through 1.41). The vulnerability is triggered by sending a pre-authentication IMAP command with a crafted parameter and an excessively long string, leading to a buffer overflow condition. This flaw allows remote attackers to execute arbitrary code on the affected system prior to authentication.
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 exploit module targeting a buffer overflow vulnerability (CVE-2006-6423) in the IMAP LOGIN command of MailEnable IMAPD versions 2.34 and 2.35 on Windows. The exploit connects to the IMAP service on TCP port 143, sends a crafted LOGIN command to trigger a buffer overflow, and injects a customizable Metasploit payload (up to 450 bytes, avoiding certain bad characters). The module supports two specific target versions, each with its own return address. Successful exploitation results in arbitrary code execution with the privileges of the IMAPD service. The code is written in Ruby and follows the standard Metasploit module structure.
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.