First published: Mon Sep 30 2013(Updated: )
The strHdrAcptLangGetItem function in errorpage.cc in Squid 3.2.x before 3.2.9 and 3.3.x before 3.3.3 allows remote attackers to cause a denial of service (infinite loop and CPU consumption) via a "," character in an Accept-Language header.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Squid Web Proxy Cache | =3.2.0.1 | |
Squid Web Proxy Cache | =3.2.0.2 | |
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.3.0 | |
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 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-1839 has a high severity rating as it leads to denial of service through CPU exhaustion.
To fix CVE-2013-1839, upgrade your Squid instance to version 3.2.9 or 3.3.3 or later.
CVE-2013-1839 affects Squid versions 3.2.x prior to 3.2.9 and 3.3.x prior to 3.3.3.
CVE-2013-1839 allows attackers to exploit a vulnerability in the Accept-Language header, causing an infinite loop.
Yes, CVE-2013-1839 can be exploited remotely by sending a specially crafted Accept-Language header.