CVE-2016-10003: Infoleak

Published Jan 27, 2017
·
Updated

Incorrect HTTP Request header comparison in Squid HTTP Proxy 3.5.0.1 through 3.5.22, and 4.0.1 through 4.0.16 results in Collapsed Forwarding feature mistakenly identifying some private responses as being suitable for delivery to multiple clients.

Affected Software

44 affected components
Squid-Cache Squid=3.5.0.1
Squid-Cache Squid=3.5.0.2
Squid-Cache Squid=3.5.0.3
Squid-Cache Squid=3.5.0.4
Squid-Cache Squid=3.5.1
Squid-Cache Squid=3.5.2
Squid-Cache Squid=3.5.3
Squid-Cache Squid=3.5.4
Squid-Cache Squid=3.5.5
Squid-Cache Squid=3.5.6
Squid-Cache Squid=3.5.7
Squid-Cache Squid=3.5.8
Squid-Cache Squid=3.5.9
Squid-Cache Squid=3.5.10
Squid-Cache Squid=3.5.11
Squid-Cache Squid=3.5.12
Squid-Cache Squid=3.5.13
Squid-Cache Squid=3.5.14
Squid-Cache Squid=3.5.15
Squid-Cache Squid=3.5.16
Squid-Cache Squid=3.5.17
Squid-Cache Squid=3.5.18
Squid-Cache Squid=3.5.19
Squid-Cache Squid=3.5.20
Squid-Cache Squid=3.5.21
Squid-Cache Squid=3.5.22
Squid-Cache Squid=4.0.1
Squid-Cache Squid=4.0.2
Squid-Cache Squid=4.0.3
Squid-Cache Squid=4.0.4
Squid-Cache Squid=4.0.5
Squid-Cache Squid=4.0.6
Squid-Cache Squid=4.0.7
Squid-Cache Squid=4.0.8
Squid-Cache Squid=4.0.9
Squid-Cache Squid=4.0.10
Squid-Cache Squid=4.0.11
Squid-Cache Squid=4.0.12
Squid-Cache Squid=4.0.13
Squid-Cache Squid=4.0.14
Squid-Cache Squid=4.0.15
Squid-Cache Squid=4.0.16
Squid-Cache Squid>=3.5.0.1<3.5.23
Squid-Cache Squid>=4.0.1<4.0.17

Event History

Jan 27, 2017
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
Description
Data Sourced
via NVD·05:59 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2016-10003?

CVE-2016-10003 is classified as a moderate severity vulnerability due to its potential impact on data privacy.

2

How do I fix CVE-2016-10003?

To fix CVE-2016-10003, upgrade Squid HTTP Proxy to version 3.5.23 or newer, or 4.0.17 or newer.

3

What software versions are affected by CVE-2016-10003?

CVE-2016-10003 affects Squid HTTP Proxy versions from 3.5.0.1 to 3.5.22 and 4.0.1 to 4.0.16.

4

Is CVE-2016-10003 easy to exploit?

Exploitation of CVE-2016-10003 may require a specific configuration, but could lead to unintended data exposure.

5

What are the implications of CVE-2016-10003?

CVE-2016-10003 can result in private responses being delivered to multiple clients, compromising confidentiality.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203