Loading vulnerability…
SpamAssassin versions before 3.1.3 contain an OS command injection vulnerability when used with vpopmail and the paranoid (-P) switch. A crafted message can cause improper handling of the virtual POP username during invocation of spamd, enabling execution of arbitrary commands.
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 exploit module targeting a remote command execution vulnerability in the SpamAssassin spamd service (CVE-2006-2447). The exploit abuses the handling of the 'User' header when spamd is running with vpopmail and paranoid modes enabled (a non-default configuration) on versions prior to 3.1.3. The module connects to the spamd service over TCP port 783, sends a specially crafted request with a malicious 'User' header containing the attacker's payload, and triggers arbitrary command execution as the user running spamd. The payload is customizable and supports various command types (bash, perl, ruby, telnet, etc.) as provided by the Metasploit framework. The repository is structured as a single Ruby file compatible with Metasploit, and is operational, allowing attackers to gain remote code execution on vulnerable systems.
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.