HTTP Request Smuggling Affecting squid:4/libecap package, versions <0:1.0.1-2.module_el8.6.0+2741+01592ae8


Severity

Recommended
0.0
medium
0
10

Based on AlmaLinux security rating.

Threat Intelligence

EPSS
10.77% (93rd 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-ALMALINUX8-SQUID-5617095
  • published28 May 2023
  • disclosed3 Nov 2020

Introduced: 3 Nov 2020

CVE-2019-18678  (opens in a new tab)
CWE-444  (opens in a new tab)

How to fix?

Upgrade AlmaLinux:8 squid:4/libecap to version 0:1.0.1-2.module_el8.6.0+2741+01592ae8 or higher.
This issue was patched in ALSA-2020:4743.

NVD Description

Note: Versions mentioned in the description apply only to the upstream squid:4/libecap package and not the squid:4/libecap package as distributed by AlmaLinux. See How to fix? for AlmaLinux:8 relevant fixed versions and status.

An issue was discovered in Squid 3.x and 4.x through 4.8. It allows attackers to smuggle HTTP requests through frontend software to a Squid instance that splits the HTTP Request pipeline differently. The resulting Response messages corrupt caches (between a client and Squid) with attacker-controlled content at arbitrary URLs. Effects are isolated to software between the attacker client and Squid. There are no effects on Squid itself, nor on any upstream servers. The issue is related to a request header containing whitespace between a header name and a colon.

CVSS Base Scores

version 3.1