Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1405943 - (CVE-2016-10003) CVE-2016-10003 squid: Information disclosure in Collapsed forwarding
CVE-2016-10003 squid: Information disclosure in Collapsed forwarding
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20161216,reported=2...
: Security
Depends On: 1405944
Blocks: 1405945
  Show dependency treegraph
 
Reported: 2016-12-19 04:10 EST by Andrej Nemec
Modified: 2017-01-12 11:27 EST (History)
7 users (show)

See Also:
Fixed In Version: squid 3.5.23, squid 4.0.17
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-01-12 11:27:30 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Andrej Nemec 2016-12-19 04:10:50 EST
Due to incorrect comparsion of request headers Squid can deliver responses containing private data to clients it should not have reached.

This problem allows a remote attacker to discover private and sensitive information about another clients browsing session. Potentially including credentials which allow access to further sensitive resources.

This problem only affects Squid configured to use the Collapsed Forwarding feature. It is of particular importance for HTTPS reverse-proxy sites with Collapsed Forwarding.

External References:

http://www.squid-cache.org/Advisories/SQUID-2016_10.txt

References:

http://seclists.org/oss-sec/2016/q4/699
Comment 1 Andrej Nemec 2016-12-19 04:11:57 EST
Created squid tracking bugs for this issue:

Affects: fedora-all [bug 1405944]
Comment 4 Cedric Buissart 2017-01-12 11:26:37 EST
Statement:

Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

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