First published: Mon Aug 24 2020(Updated: )
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.
Credit: cve@mitre.org cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
debian/squid | <=4.12-1<=4.6-1<=4.6-1+deb10u3 | 4.13-1 4.6-1+deb10u4 |
debian/squid | 4.13-10+deb11u3 5.7-2+deb12u2 6.10-1 | |
Squid Web Proxy Cache | <4.13 | |
Squid Web Proxy Cache | >=5.0<5.0.4 | |
Ubuntu Linux | =16.04 | |
Ubuntu Linux | =18.04 | |
Ubuntu Linux | =20.04 | |
Debian Debian Linux | =9.0 | |
Debian Debian Linux | =10.0 | |
Fedoraproject Fedora | =31 | |
Fedoraproject Fedora | =32 | |
Fedoraproject Fedora | =33 | |
openSUSE | =15.1 | |
openSUSE | =15.2 | |
IBM InfoSphere Guardium z/OS | <=10.5 | |
IBM InfoSphere Guardium z/OS | <=10.6 | |
IBM InfoSphere Guardium z/OS | <=11.0 | |
IBM InfoSphere Guardium z/OS | <=11.1 | |
IBM InfoSphere Guardium z/OS | <=11.2 | |
IBM InfoSphere Guardium z/OS | <=11.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID of this issue is CVE-2020-15811.
The severity of CVE-2020-15811 is medium.
The affected software is Squid-Cache Squid versions before 4.13 and 5.x before 5.0.4.
This vulnerability allows HTTP Request Splitting attacks to succeed against HTTP and HTTPS traffic, leading to cache poisoning.
To fix CVE-2020-15811, upgrade to Squid version 4.13 or 5.0.4 or later.