Bug 626933 - Squid: Buffer overread when processing large DNS replies with no IPv6 resolver present [fedora-all]
Summary: Squid: Buffer overread when processing large DNS replies with no IPv6 resolve...
Alias: None
Product: Fedora
Classification: Fedora
Component: squid
Version: 13
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Jiri Skala
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: CVE-2010-2951
TreeView+ depends on / blocked
Reported: 2010-08-24 17:39 UTC by Jan Lieskovsky
Modified: 2014-11-09 22:33 UTC (History)
4 users (show)

Fixed In Version: 3.1.7-1
Doc Type: Release Note
Doc Text:
Clone Of:
Last Closed: 2010-08-24 20:07:25 UTC
Type: ---

Attachments (Terms of Use)

Description Jan Lieskovsky 2010-08-24 17:39:40 UTC
This is an automatically created tracking bug!  It was created to ensure
that one or more security vulnerabilities are fixed in affected Fedora

For comments that are specific to the vulnerability please use bugs filed
against "Security Response" product referenced in the "Blocks" field.

For more information see:

When creating a Bodhi update request, please include the bug IDs of the
respective parent bugs filed against the "Security Response" product.
Please mention CVE ids in the RPM changelog when available.

Bodhi update submission link:

Please note: this issue affects multiple supported versions of Fedora.
Only one tracking bug has been filed; please only close it when all
affected versions are fixed.

[bug automatically created by: add-tracking-bugs]

Comment 1 Henrik Nordström 2010-08-24 18:06:32 UTC
Affected updates-testing release unpushed from updates-testing for F14,F13,F12.

See also my comments on the Security Response regarding this issue in general.

Comment 2 Henrik Nordström 2010-08-24 20:06:01 UTC
Squid-3.1.7-1 has been submitted for updates-testing which fixes this. I did not tag the update with this bug however as the bug only affects the previous test update which got pushed yesterday. If you wish then I am happy to tag the 3.1.7-1 update with this bug, but it does not seem right to say it's a security update when

a) Users running the stable updates are not affected, only users using updates-testing as of yesterday.
b) The nature of the bug in question.

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