Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.GSO.4.51.0902081629490.25237@faron.mitre.org>
Date: Sun, 8 Feb 2009 16:31:00 -0500 (EST)
From: "Steven M. Christey" <coley@...us.mitre.org>
To: oss-security@...ts.openwall.com
cc: Josh Bressers <bressers@...hat.com>, coley@...re.org
Subject: Re: CVE request: Squid <2.7.6, 3.0.13, 3.1.0.5 DoS


I do subscribe to oss-security so see these emails.  Still working on the
best process to be able to respond more quickly.

The SQUID advisory doesn't state what kind of DoS it is, and it's not
clear from the patches either.  Is it a crash, hang, resource consumption,
etc.?  Not essential from a CVE perspective but probanly convenient to
Squid users.

- Steve

======================================================
Name: CVE-2009-0478
Status: Candidate
URL: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0478
Reference: CONFIRM:http://www.squid-cache.org/Advisories/SQUID-2009_1.txt
Reference: CONFIRM:http://www.squid-cache.org/Versions/v2/2.7/changesets/12432.patch

Squid 2.7 to 2.7.STABLE5, 3.0 to 3.0.STABLE12, and 3.1 to 3.1.0.4
allows remote attackers to cause a denial of service via an HTTP
request with an invalid version number, which is not properly handled
in (1) HttpMsg.c and (2) HttpStatusLine.c.


Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.