|Description||An issue was discovered in Squid before 4.13 and 5.x before 5.0.4. Due to incorrect data validation, HTTP Request Splitting attacks may succeed against HTTP and HTTPS traffic. This leads to cache poisoning. This allows any client, including browser scripts, to bypass local security and poison the browser cache and any downstream caches with content from an arbitrary source. Squid uses a string search instead of parsing the Transfer-Encoding header to find chunked encoding. This allows an attacker to hide a second request inside Transfer-Encoding: it is interpreted by Squid as chunked and split out into a second request delivered upstream. Squid will then deliver two distinct responses to the client, corrupting any downstream caches.|
|Source||CVE (at NVD; CERT, LWN, oss-sec, fulldisc, bugtraq, EDB, Metasploit, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, Mageia, GitHub code/issues, web search, more)|
|References||DLA-2394-1, DSA-4751-1, ELA-294-1|
Vulnerable and fixed packages
The table below lists information on source packages.
|bullseye (security), bullseye||4.13-10+deb11u2||fixed|
|squid3 (PTS)||jessie, jessie (lts)||3.5.23-5+deb8u6||fixed|
|stretch (lts), stretch||3.5.23-5+deb9u9||fixed|
The information below is based on the following data on fixed versions.
Squid 4: http://www.squid-cache.org/Versions/v4/changesets/SQUID-2020_8.patch