Bugzilla will be upgraded to version 5.0 on December 2, 2018. The outage period for the upgrade will start at 0:00 UTC and have a duration of 12 hours
Bug 484246 - (CVE-2009-0478) CVE-2009-0478 Squid denial of service flaw
CVE-2009-0478 Squid denial of service flaw
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
Depends On: 484781 484782
  Show dependency treegraph
Reported: 2009-02-05 11:24 EST by Josh Bressers
Modified: 2009-02-13 08:17 EST (History)
4 users (show)

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

Attachments (Terms of Use)

  None (edit)
Description Josh Bressers 2009-02-05 11:24:59 EST
A denial of service flaw was found in the way squid handles certain client initiated requests. A client who can connect to the squid server could leverage this flaw to cause the squid child process to terminate. This would prevent anyone from using the squid server until the process automatically restarts.
Comment 2 Josh Bressers 2009-02-05 11:40:18 EST
The issue here is that a client request could be constructed in such a way that it triggers a call to assert() in the squid child process.  This then causes the child process to quit, stopping all current requests until the child process is restarted.

As this end up calling assert(), there is no potential for code execution from this particular flaw.

The code that triggers this flaw is only present in squid versions 2.7 and above.
Comment 5 Tomas Hoger 2009-02-11 02:31:51 EST
Official Statement from Red Hat (02/09/2009)
    Not vulnerable. This issue did not affect the version of Squid as
    shipped with Red Hat Enterprise Linux 2.1, 3, 4, or 5.

Comment 6 Red Hat Product Security 2009-02-13 08:17:08 EST
This issue was addressed in:


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