Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 228586 - CVE-2007-0451 Spamassassin DoS
CVE-2007-0451 Spamassassin DoS
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: spamassassin (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Warren Togami
: Security
Depends On:
  Show dependency treegraph
Reported: 2007-02-13 16:29 EST by Mark J. Cox
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version: RHSA-2007-0074
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-02-21 13:44:52 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2007:0074 normal SHIPPED_LIVE Important: spamassassin security update 2007-02-21 13:44:50 EST

  None (edit)
Description Mark J. Cox 2007-02-13 16:29:22 EST
There is a DoS in apparantly all versions of spamassassin prior to
3.1.8 (which is not released yet).  A carefully crafted message can 
cause SpamAssassin to consume significant resources which could lead
to a DoS if an attacker sends many such messages:


Also affects RHEL4.

Patch here:
Comment 3 Josh Bressers 2007-02-13 22:58:22 EST
I presume this flaw affects RHEL3 as well.  Is the plan to upgrade to
spamassassin 3.1.8, or to backport this fix?
Comment 5 Warren Togami 2007-02-14 17:04:48 EST
It appears we lucked out.  RHEL3 is not effected in such a dangerous way.  Just
a slight delay, and no huge CPU or memory usage.  I suspect we need not touch it
for this CVE.  Will do further verification.

Upstream is releasing 3.1.8 today, and I am pushing it to Fedora now.
Comment 7 Josh Bressers 2007-02-21 12:38:52 EST
Lifting Embargo
Comment 8 Red Hat Bugzilla 2007-02-21 13:44:52 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.