CVE-2020-15811

Medium

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.

SeverityMedium
CVSS6.5
Exploit probability—
ProductSquid
PublishedSep 2, 2020
First seenSep 2, 2020

How to fix

Affected products

ProductAffected versionsFixed in
squid-cache squidv < 4.13, 5.0 ≤ v < 5.0.44.13, 5.0.4
canonical ubuntu_linux16.04, 18.04, 20.04—
debian debian_linux9.0, 10.0—
fedoraproject fedora31, 32, 33—
opensuse leap15.1, 15.2—

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.