Insufficient Comparison 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.15% (53rd 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-2557853
  • published10 Apr 2022
  • disclosed2 Sept 2020

Introduced: 2 Sep 2020

CVE-2020-15811  (opens in a new tab)
CWE-697  (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 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.

References

CVSS Scores

version 3.1