Out-of-bounds Read 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-2022:1939</code>.</p>

Threat Intelligence

5.66% (94^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-LIBECAP-3205665
published 5 Jan 2023
disclosed 9 Mar 2021

Report a new vulnerability Found a mistake?

Introduced: 9 Mar 2021

CVE-2021-28116 Open this link in a new tab CWE-125 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-2022:1939.

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.

Squid through 4.14 and 5.x through 5.0.5, in some configurations, allows information disclosure because of an out-of-bounds read in WCCP protocol data. This can be leveraged as part of a chain for remote code execution as nobody.

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)

Low
Integrity (I)

None
Availability (A)

None

Out-of-bounds Read Affecting libecap package, versions <0:1.0.1-2.module+el8.4.0+404+316a0dc5

Severity

Based on Rocky Linux security rating