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.
Metrics
Affected Vendors & Products
Advisories
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-2394-1 | squid3 security update |
Debian DSA |
DSA-4751-1 | squid security update |
Ubuntu USN |
USN-4477-1 | Squid vulnerabilities |
Ubuntu USN |
USN-4551-1 | Squid vulnerabilities |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-08-04T13:30:22.344Z
Reserved: 2020-07-17T00:00:00
Link: CVE-2020-15811
No data.
Status : Modified
Published: 2020-09-02T17:15:11.687
Modified: 2024-11-21T05:06:13.753
Link: CVE-2020-15811
OpenCVE Enrichment
No data.
Debian DLA
Debian DSA
Ubuntu USN