Bug 126863 - CAN-2004-0493 folding header DoS
Summary: CAN-2004-0493 folding header DoS
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: httpd
Version: 3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Joe Orton
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-06-28 15:20 UTC by Mark J. Cox
Modified: 2007-11-30 22:07 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-07-06 08:34:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2004:342 0 high SHIPPED_LIVE Important: httpd security update 2004-07-06 04:00:00 UTC

Description Mark J. Cox 2004-06-28 15:20:03 UTC
Apache 2.0.49 places no limit on the amount of folding of input
headers, or in the total length after folding.  With an input stream
with infinite headers to be folded, the server will allocate as much
memory as the system will allow, possibly leading to a denial of
service.  

Public by Georgi Guninski to full-disclosure on Jun28

        CAN-2004-0493 Affects: 3AS 3WS 3ES 3Desktop

Comment 1 Jacek Piskozub 2004-06-30 05:48:41 UTC
The original report by Guninski is to be found at
http://www.guninski.com/httpd1.html

Comment 2 Neil Horman 2004-07-01 14:48:50 UTC
Quick thought for a workaround while this gets straigtened out:

Use ulimit -d to limit the amount of data memory that any one httpd
process can have. Make it high enough to function for whatever purpose
you use httpd for, but lower than all of memory (i.e. unlimited)

I can recall if allocations above 'ulimit -d' core out the process or
return ENOMEM, but if they do the former, enable core files, and write
a cron job to clean up and restart any crashed httpd processes.  This
should prevent significant system slow down, and allow for a modest
prevention of the DoS attack.

Comment 3 Mark J. Cox 2004-07-06 08:34:34 UTC
An errata 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-2004-342.html



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