HTTP Request Smuggling Affecting squid package, versions <7:4.4-8.module+el8.2.0+7778+aff7482f.2


Severity

Recommended
high

Based on Oracle Linux security rating.

Threat Intelligence

EPSS
0.19% (58th 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-ORACLE8-SQUID-2557975
  • published10 Apr 2022
  • disclosed2 Sept 2020

Introduced: 2 Sep 2020

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

How to fix?

Upgrade Oracle:8 squid to version 7:4.4-8.module+el8.2.0+7778+aff7482f.2 or higher.
This issue was patched in ELSA-2020-3623.

NVD Description

Note: Versions mentioned in the description apply only to the upstream squid package and not the squid package as distributed by Oracle. See How to fix? for Oracle: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 Smuggling 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 proxy cache and any downstream caches with content from an arbitrary source. When configured for relaxed header parsing (the default), Squid relays headers containing whitespace characters to upstream servers. When this occurs as a prefix to a Content-Length header, the frame length specified will be ignored by Squid (allowing for a conflicting length to be used from another Content-Length header) but relayed upstream.

References

CVSS Scores

version 3.1