Bug 626933

Summary:	Squid: Buffer overread when processing large DNS replies with no IPv6 resolver present [fedora-all]
Product:	[Fedora] Fedora	Reporter:	Jan Lieskovsky <jlieskov>
Component:	squid	Assignee:	Jiri Skala <jskala>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	13	CC:	aglotov, henrik, jonathansteffan, jskala
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	3.1.7-1	Doc Type:	Release Note
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-08-24 20:07:25 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	626927

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
versions.

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:
http://fedoraproject.org/wiki/Security/TrackingBugs

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:
https://admin.fedoraproject.org/updates/new/?type_=security&bugs=626927

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.