Skip to content
Fencer Vulns
medium 5.1

CVE-2006-2447 json

SpamAssassin before 3.1.3, when running with vpopmail and the paranoid (-P) switch, allows remote attackers to execute arbitrary commands v…

published 2006-06-06 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-2448

cvss
5.1
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
75.8%
EPSS 75.8% chance of exploitation in 30 days, percentile 99.5%
public exploits
3
Metasploit, Exploit-DB

Summary

SpamAssassin before 3.1.3, when running with vpopmail and the paranoid (-P) switch, allows remote attackers to execute arbitrary commands via a crafted message that is not properly handled when invoking spamd with the virtual pop username.

Patch / fix

  • spamassassin Debian 14, Debian 13, Debian 12 3.1.3-1

debian advisories DEBIAN-CVE-2006-2447

  • spamassassin RHEL 4 3.0.6-1.el4

red hat advisories RHSA-2006:0543

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2006-2447 updated

security flaw

  • Red Hat Enterprise Linux AS version 4 spamassassin 3.0.6-1.el4 Red Hat Enterprise Linux Desktop version 4 spamassassin 3.0.6-1.el4 Red Hat Enterprise Linux ES version 4 spamassassin 3.0.6-1.el4 Red Hat Enterprise Linux WS version 4 spamassassin 3.0.6-1.el4
    fixed: vendor fix RHSA-2006:0543

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. First public exploit (Metasploit exploit/unix/misc/spamassassin_exec)
  2. Published

Exploit prediction

75.81% chance of exploitation in the next 30 days, higher than 99.5% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

CVSS scores

assigned by version score vector
NVD 2.0 5.1 AV:N/AC:H/Au:N/C:P/I:P/A:P

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.