Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 23 Feb 2015 00:37:09 +1300
From: Amos Jeffries <>
Subject: Re: CVE-2015-0881

Hash: SHA1

On 22/02/2015 7:17 p.m., Kurt Seifried wrote:
> I'm trying to track down information on CVE-2015-0881.
> I can't find a squid security contact ( 
> bounced), there's no security report, and no link to a source code
> patch for this.

- From the "Contact Us page"

  squid-bugs @

... which goes to me and some other trusted developers. I dont mind
direct contacts for this type of thing, but the main contact address
guarantees someone sees it within a few hrs.

Regarding the CVE:

1) This is the first I've heard about this particular CVE number

2) I did have some discusions with JPCERT about _a_ response splitting
vulnerability around those years. But the messages from them were IIRC
about replicating response splitting in a 2.x versions which were
incompletely fixed by:
(did not get a CVE AFAIK).

3) I have not been able to replicate the #2 issue in the Squid-3
series and several iterations of changes to the parsers there have
been careful to take the above issue into account. So I'm not sure
where the 3.1.10 comes from. Assuming it is the same vulnerability.

> This is regarding 3.1.9 and earlier, 3.1.10 was released on 22 Dec
> 2010, so 4+ years ago.
> Needless to say I am more than a bit confused. A link to a specific
> code patch/vuln/file would be helpful. Also if anyone knows how to
> contact Squid re security issues properly I'd love to know.

I'm not sure 3.1.10 is the right version for attribution on any
response splitting fix. There certainly were no patches solving
anything related to respinse splitting in that version. Some
borderline memory leak vulnerabilities perhapse, but not response

NP: Just to confuse things there was a major replacement of the HTTP
request-line parser on the 2015-02-10 which does explicitly fix all
lot of known HTTP request-line parse issues, including a few response
splitting vectors using downgrade to HTTP/0.9 handling. That will only
be in the 3.6 series though.

Amos Jeffries
Squid Software Foundation

Version: GnuPG v2.0.22 (MingW32)


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.