high
7.5
CWE
200
Advisory Published
Updated

CVE-2016-10002: Infoleak

First published: Fri Jan 27 2017(Updated: )

Incorrect processing of responses to If-None-Modified HTTP conditional requests in Squid HTTP Proxy 3.1.10 through 3.1.23, 3.2.0.3 through 3.5.22, and 4.0.1 through 4.0.16 leads to client-specific Cookie data being leaked to other clients. Attack requests can easily be crafted by a client to probe a cache for this information.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
Debian GNU/Linux=8.0
Squid Web Proxy Cache=3.1.10
Squid Web Proxy Cache=3.1.11
Squid Web Proxy Cache=3.1.12
Squid Web Proxy Cache=3.1.14
Squid Web Proxy Cache=3.1.15
Squid Web Proxy Cache=3.1.16
Squid Web Proxy Cache=3.1.17
Squid Web Proxy Cache=3.1.18
Squid Web Proxy Cache=3.1.19
Squid Web Proxy Cache=3.1.20
Squid Web Proxy Cache=3.1.21
Squid Web Proxy Cache=3.1.22
Squid Web Proxy Cache=3.1.23
Squid Web Proxy Cache=3.2.0.3
Squid Web Proxy Cache=3.2.0.4
Squid Web Proxy Cache=3.2.0.5
Squid Web Proxy Cache=3.2.0.6
Squid Web Proxy Cache=3.2.0.7
Squid Web Proxy Cache=3.2.0.8
Squid Web Proxy Cache=3.2.0.9
Squid Web Proxy Cache=3.2.0.10
Squid Web Proxy Cache=3.2.0.11
Squid Web Proxy Cache=3.2.0.12
Squid Web Proxy Cache=3.2.0.13
Squid Web Proxy Cache=3.2.0.14
Squid Web Proxy Cache=3.2.0.15
Squid Web Proxy Cache=3.2.0.16
Squid Web Proxy Cache=3.2.0.17
Squid Web Proxy Cache=3.2.0.18
Squid Web Proxy Cache=3.2.0.19
Squid Web Proxy Cache=3.2.1
Squid Web Proxy Cache=3.2.2
Squid Web Proxy Cache=3.2.3
Squid Web Proxy Cache=3.2.4
Squid Web Proxy Cache=3.2.5
Squid Web Proxy Cache=3.2.6
Squid Web Proxy Cache=3.2.7
Squid Web Proxy Cache=3.2.8
Squid Web Proxy Cache=3.2.9
Squid Web Proxy Cache=3.2.10
Squid Web Proxy Cache=3.2.11
Squid Web Proxy Cache=3.2.12
Squid Web Proxy Cache=3.2.13
Squid Web Proxy Cache=3.2.14
Squid Web Proxy Cache=3.3.0.1
Squid Web Proxy Cache=3.3.0.2
Squid Web Proxy Cache=3.3.0.3
Squid Web Proxy Cache=3.3.1
Squid Web Proxy Cache=3.3.2
Squid Web Proxy Cache=3.3.3
Squid Web Proxy Cache=3.3.4
Squid Web Proxy Cache=3.3.5
Squid Web Proxy Cache=3.3.6
Squid Web Proxy Cache=3.3.7
Squid Web Proxy Cache=3.3.8
Squid Web Proxy Cache=3.3.9
Squid Web Proxy Cache=3.3.10
Squid Web Proxy Cache=3.3.11
Squid Web Proxy Cache=3.3.12
Squid Web Proxy Cache=3.3.13
Squid Web Proxy Cache=3.3.14
Squid Web Proxy Cache=3.4.0.1
Squid Web Proxy Cache=3.4.0.2
Squid Web Proxy Cache=3.4.0.3
Squid Web Proxy Cache=3.4.0.4
Squid Web Proxy Cache=3.4.1
Squid Web Proxy Cache=3.4.2
Squid Web Proxy Cache=3.4.3
Squid Web Proxy Cache=3.4.4
Squid Web Proxy Cache=3.4.5
Squid Web Proxy Cache=3.4.6
Squid Web Proxy Cache=3.4.7
Squid Web Proxy Cache=3.4.8
Squid Web Proxy Cache=3.4.9
Squid Web Proxy Cache=3.4.10
Squid Web Proxy Cache=3.4.11
Squid Web Proxy Cache=3.4.12
Squid Web Proxy Cache=3.4.13
Squid Web Proxy Cache=3.4.14
Squid Web Proxy Cache=3.5.0.1
Squid Web Proxy Cache=3.5.0.2
Squid Web Proxy Cache=3.5.0.3
Squid Web Proxy Cache=3.5.0.4
Squid Web Proxy Cache=3.5.1
Squid Web Proxy Cache=3.5.2
Squid Web Proxy Cache=3.5.3
Squid Web Proxy Cache=3.5.4
Squid Web Proxy Cache=3.5.5
Squid Web Proxy Cache=3.5.6
Squid Web Proxy Cache=3.5.7
Squid Web Proxy Cache=3.5.8
Squid Web Proxy Cache=3.5.9
Squid Web Proxy Cache=3.5.10
Squid Web Proxy Cache=3.5.11
Squid Web Proxy Cache=3.5.12
Squid Web Proxy Cache=3.5.13
Squid Web Proxy Cache=3.5.14
Squid Web Proxy Cache=3.5.15
Squid Web Proxy Cache=3.5.16
Squid Web Proxy Cache=3.5.17
Squid Web Proxy Cache=3.5.18
Squid Web Proxy Cache=3.5.19
Squid Web Proxy Cache=3.5.20
Squid Web Proxy Cache=3.5.21
Squid Web Proxy Cache=3.5.22
Squid Web Proxy Cache=4.0.1
Squid Web Proxy Cache=4.0.2
Squid Web Proxy Cache=4.0.3
Squid Web Proxy Cache=4.0.4
Squid Web Proxy Cache=4.0.5
Squid Web Proxy Cache=4.0.6
Squid Web Proxy Cache=4.0.7
Squid Web Proxy Cache=4.0.8
Squid Web Proxy Cache=4.0.9
Squid Web Proxy Cache=4.0.10
Squid Web Proxy Cache=4.0.11
Squid Web Proxy Cache=4.0.12
Squid Web Proxy Cache=4.0.13
Squid Web Proxy Cache=4.0.14
Squid Web Proxy Cache=4.0.15
Squid Web Proxy Cache=4.0.16

Remedy

http://www.openwall.com/lists/oss-security/2016/12/18/1

Remedy

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

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2016-10002?

    CVE-2016-10002 has a medium severity level due to the risk of client-specific cookie data leakage.

  • How do I fix CVE-2016-10002?

    To fix CVE-2016-10002, upgrade to the patched versions of Squid HTTP Proxy 3.5.23 or later.

  • Which versions of Squid are affected by CVE-2016-10002?

    CVE-2016-10002 affects Squid HTTP Proxy versions 3.1.10 through 3.1.23, 3.2.0.3 to 3.5.22, and 4.0.1 to 4.0.16.

  • Is CVE-2016-10002 exploitable remotely?

    Yes, CVE-2016-10002 can be exploited remotely by attackers crafting specific HTTP requests.

  • What kind of data is exposed due to CVE-2016-10002?

    CVE-2016-10002 may lead to exposure of client-specific Cookie data to other clients.

Company

Resources

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203