HTTP Request Smuggling Affecting squid-debuginfo package, versions <7:3.5.20-17.amzn2.4.1


Severity

Recommended
high

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.16% (54th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-AMZN2-SQUIDDEBUGINFO-1688387
  • published27 Sept 2021
  • disclosed2 Sept 2020

Introduced: 2 Sep 2020

CVE-2020-15811  (opens in a new tab)
CWE-444  (opens in a new tab)

How to fix?

Upgrade Amazon-Linux:2 squid-debuginfo to version 7:3.5.20-17.amzn2.4.1 or higher.
This issue was patched in ALAS2-2020-1548.

NVD Description

Note: Versions mentioned in the description apply only to the upstream squid-debuginfo package and not the squid-debuginfo package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2 relevant fixed versions and status.

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.

CVSS Scores

version 3.1