HTTP Request Smuggling Affecting squid:4/libecap-devel package, versions <0:1.0.1-2.module+el8.1.0+4044+36416a77


Severity

Recommended
high

Based on Red Hat Enterprise 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-RHEL8-SQUID-3781623
  • published26 Jul 2021
  • disclosed23 Aug 2020

Introduced: 23 Aug 2020

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

How to fix?

Upgrade RHEL:8 squid:4/libecap-devel to version 0:1.0.1-2.module+el8.1.0+4044+36416a77 or higher.
This issue was patched in RHSA-2020:3623.

NVD Description

Note: Versions mentioned in the description apply only to the upstream squid:4/libecap-devel package and not the squid:4/libecap-devel package as distributed by RHEL. See How to fix? for RHEL:8 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