CONTENTUM.COMA specialist. A plan. A result.

Vulnerabilities · 2020 · Squid-cache

CVE-2020-15811
Squid-cache Squid vulnerability

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.

Affected products

Squid, Ubuntu Linux, Debian Linux, Fedora, Leap. The exact versions are in the references.

What to do now

  • Check your exposureFind out whether Squid-cache Squid runs anywhere in your environment, including systems of suppliers.
  • UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
  • Set the orderSystems that can be reached from the internet come first, then the rest.

References

More vulnerabilities in Squid-cache products

Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.