First published: Fri 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.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Squid Web Proxy Cache | >=3.5.0.1<3.5.23 | |
Squid Web Proxy Cache | >=4.0.1<4.0.17 | |
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 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-10003 is classified as a moderate severity vulnerability due to its potential impact on data privacy.
To fix CVE-2016-10003, upgrade Squid HTTP Proxy to version 3.5.23 or newer, or 4.0.17 or newer.
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.
Exploitation of CVE-2016-10003 may require a specific configuration, but could lead to unintended data exposure.
CVE-2016-10003 can result in private responses being delivered to multiple clients, compromising confidentiality.