Skip to content
Fencer Vulns
low 1.9

CVE-2007-2873 json

SpamAssassin 3.1.x, 3.2.0, and 3.2.1 before 20070611, when running as root in unusual configurations using vpopmail or virtual users, allow…

published 2007-06-11 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-2865

cvss
1.9
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 27%
public exploits
0
none known

Summary

SpamAssassin 3.1.x, 3.2.0, and 3.2.1 before 20070611, when running as root in unusual configurations using vpopmail or virtual users, allows local users to cause a denial of service (corrupt arbitrary files) via a symlink attack on a file that is used by spamd.

Patch / fix

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

debian advisories DEBIAN-CVE-2007-2873

  • spamassassin RHEL 4 3.1.9-1.el4
  • spamassassin RHEL 5 3.1.9-1.el5

red hat advisories RHSA-2007:0492

  • spamassassin openSUSE Tumbleweed 3.4.6-71.3

opensuse advisories openSUSE-SU-2024:11395-1

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-2007-2873 updated

spamassassin symlink attack

  • Red Hat Enterprise Linux (v. 5 server) spamassassin 3.1.9-1.el5 Red Hat Enterprise Linux AS version 4 spamassassin 3.1.9-1.el4 Red Hat Enterprise Linux Desktop (v. 5 client) spamassassin 3.1.9-1.el5 Red Hat Enterprise Linux Desktop version 4 spamassassin 3.1.9-1.el4 Red Hat Enterprise Linux ES version 4 spamassassin 3.1.9-1.el4 Red Hat Enterprise Linux WS version 4 spamassassin 3.1.9-1.el4
    fixed: vendor fix RHSA-2007:0492

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

Exploit prediction

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

CVSS scores

assigned by version score vector
NVD 2.0 1.9 AV:L/AC:M/Au:N/C:N/I:N/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.