Bug 159198

Summary:	CAN-2005-1266 spamassassin DoS
Product:	Red Hat Enterprise Linux 4	Reporter:	Josh Bressers <bressers>
Component:	spamassassin	Assignee:	Warren Togami <wtogami>
Status:	CLOSED ERRATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0	CC:	security-response-team
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:	impact=moderate,source=spamassassin,reported=20050528
Fixed In Version:	RHSA-2005-498	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-06-23 19:19:30 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	158693

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

http://people.redhat.com/wtogami/temp/spamassassin/el4/
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.

http://rhn.redhat.com/errata/RHSA-2005-498.html