Loading vulnerability…
A buffer overflow vulnerability exists in the HTTPMail service of MailEnable Enterprise 1.04 and earlier and Professional 1.54 and earlier. The vulnerability is triggered by sending an overly long HTTP Authorization header, which can overflow a buffer and potentially allow remote attackers to execute arbitrary code on the affected system.
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 targeting a buffer overflow vulnerability in the MailEnable web service (mehttps.exe) on Windows. The exploit works by sending an HTTP request with an overly long Authorization header, triggering a buffer overflow and allowing arbitrary code execution. The module is operational and allows the attacker to deliver any Metasploit-supported payload (such as a reverse shell) to the vulnerable service. The exploit targets MailEnable Enterprise Edition versions prior to 1.0.5 and Professional versions prior to 1.55, as referenced by CVE-2005-1348. The main attack vector is network-based, requiring access to the HTTP(S) service exposed by the vulnerable MailEnable installation. 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.