Memory Leak Affecting libecap-devel 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-devel</code> to version 0:1.0.1-2.module+el8.4.0+404+316a0dc5 or higher.<br>This issue was patched in <code>RLSA-2021:4292</code>.</p>

Threat Intelligence

1.55% (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-ROCKY8-LIBECAPDEVEL-3214485
published 5 Jan 2023
disclosed 27 May 2021

Report a new vulnerability Found a mistake?

Introduced: 27 May 2021

CVE-2021-28651 Open this link in a new tab CWE-401 Open this link in a new tab

How to fix?

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

NVD Description

Note: Versions mentioned in the description apply only to the upstream libecap-devel package and not the libecap-devel 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 before 4.15 and 5.x before 5.0.6. Due to a buffer-management bug, it allows a denial of service. When resolving a request with the urn: scheme, the parser leaks a small amount of memory. However, there is an unspecified attack methodology that can easily trigger a large amount of memory consumption.

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

Memory Leak Affecting libecap-devel package, versions <0:1.0.1-2.module+el8.4.0+404+316a0dc5

Severity

Based on Rocky Linux security rating