Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 159198 - CAN-2005-1266 spamassassin DoS
Summary: CAN-2005-1266 spamassassin DoS
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: spamassassin
Version: 4.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Warren Togami
QA Contact:
Whiteboard: impact=moderate,source=spamassassin,r...
Depends On:
Blocks: spamassassin_RHEL4
TreeView+ depends on / blocked
Reported: 2005-05-31 14:47 UTC by Josh Bressers
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version: RHSA-2005-498
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-06-23 19:19:30 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2005:498 normal SHIPPED_LIVE Moderate: spamassassin security update 2005-06-23 04:00:00 UTC

Description Josh Bressers 2005-05-31 14:47:09 UTC
When SA parses a message, it needs to know when the headers end and the
body begins.  In the current 3.0 code, we assume that the header ends at
either a blank line (normal) or when we see a MIME boundary.  The problem
is that we parse the Content-Type header so we can figure out what the
boundary string is, and if SA receives an extremely long Content-Type
header (especially one with tons of whitespace folding/continuation)
that doesn't have a boundary in it (or it's at the end), parsing it over
and over causes lots of wasted CPU time.

Comment 1 Josh Bressers 2005-05-31 14:48:20 UTC
This issue should also affect RHEL2.1 and RHEL3

Comment 2 Warren Togami 2005-06-06 06:21:32 UTC
Test package, waiting for decision about embargo lift on details

Comment 3 Josh Bressers 2005-06-06 20:05:48 UTC
I was wrong, this issue does not affect RHEL2.1 or RHEL3

Comment 6 Josh Bressers 2005-06-23 19:19:30 UTC
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.