HTTP Request Smuggling Affecting libecap package, versions <0:1.0.1-2.module+el8.4.0+404+316a0dc5

Q: How to fix?

<p>Upgrade <code>Rocky-Linux:8</code> <code>libecap</code> to version 0:1.0.1-2.module+el8.4.0+404+316a0dc5 or higher.<br>This issue was patched in <code>RLSA-2020:4743</code>.</p>

Threat Intelligence

0.75% (82^nd 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 ID SNYK-ROCKY8-LIBECAP-3297048
published 3 Feb 2023
disclosed 26 Nov 2019

Report a new vulnerability Found a mistake?

Introduced: 26 Nov 2019

CVE-2019-18678 Open this link in a new tab CWE-444 Open this link in a new tab

How to fix?

Upgrade Rocky-Linux:8 libecap to version 0:1.0.1-2.module+el8.4.0+404+316a0dc5 or higher.
This issue was patched in RLSA-2020:4743.

NVD Description

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

References

CVSS Scores

version 3.1

Attack Vector (AV)

Network
Attack Complexity (AC)

Low
Privileges Required (PR)

None
User Interaction (UI)

None

Scope (S)

Unchanged

Confidentiality (C)

None
Integrity (I)

Low
Availability (A)

None