CVE-2020-15811

squid: HTTP Request Splitting could result in cache poisoning

Published Sep 2, 2020 CVSS 3.1 · 6.5 Medium EPSS 3.8% KEV · Not listed
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-2394-1 squid3 security update
Debian DSA Debian DSA DSA-4751-1 squid security update
Ubuntu USN Ubuntu USN USN-4477-1 Squid vulnerabilities
Ubuntu USN Ubuntu USN USN-4551-1 Squid vulnerabilities
History

No history.