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.
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
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2024-08-04T13:30:22.344Z

Reserved: 2020-07-17T00:00:00

Link: CVE-2020-15811

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2020-09-02T17:15:11.687

Modified: 2024-11-21T05:06:13.753

Link: CVE-2020-15811

cve-icon Redhat

Severity : Important

Publid Date: 2020-08-23T00:00:00Z

Links: CVE-2020-15811 - Bugzilla

cve-icon OpenCVE Enrichment

No data.