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

Q: How to fix?

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

Threat Intelligence

1.45% (88^th 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-ALMALINUX8-SQUID-5617136
published 28 May 2023
disclosed 3 Nov 2020

Report a new vulnerability Found a mistake?

Introduced: 3 Nov 2020

CVE-2020-24606 Open this link in a new tab CWE-667 Open this link 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.

Squid before 4.13 and 5.x before 5.0.4 allows a trusted peer to perform Denial of Service by consuming all available CPU cycles during handling of a crafted Cache Digest response message. This only occurs when cache_peer is used with the cache digests feature. The problem exists because peerDigestHandleReply() livelocking in peer_digest.cc mishandles EOF.

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)

None
Availability (A)

High

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

Severity

Based on AlmaLinux security rating