CVE-2006-6761 is a stack-based buffer overflow in the IMAP daemon (IMAPD) in Novell NetMail before version 3.52e FTF2. The flaw is triggered when the server processes an overly long argument supplied to the IMAP SUBSCRIBE command. Because the vulnerable input is copied into a stack-based buffer without sufficient bounds checking, a remote authenticated user can corrupt stack memory and potentially redirect execution flow, resulting in arbitrary code execution. The issue also presents a denial-of-service risk if exploitation only crashes the daemon or underlying service.
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 exploit module targeting a stack buffer overflow vulnerability in Novell NetMail 3.52's IMAP SUBSCRIBE command (CVE-2006-6761). The exploit is implemented in Ruby and leverages the Metasploit framework's IMAP mixin to interact with the target service. The module constructs a specially crafted IMAP SUBSCRIBE command with an overly long argument, causing a buffer overflow and allowing the attacker to execute arbitrary code on the target Windows 2000 system. The payload is customizable (up to 500 bytes) and avoids problematic characters. The exploit requires network access to the IMAP service (typically TCP port 143). The repository is structured as a single exploit file within the Metasploit framework, and its purpose is to provide a remote code execution capability against vulnerable Novell NetMail IMAP servers.
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.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.