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


Severity

Recommended
0.0
medium
0
10

Based on Rocky Linux security rating

    Threat Intelligence

    EPSS
    1.06% (85th 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-3297021
  • published 3 Feb 2023
  • disclosed 11 Jul 2019

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-2020:4743.

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 2.x through 2.7.STABLE9, 3.x through 3.5.28, and 4.x through 4.7. When Squid is configured to use Basic Authentication, the Proxy-Authorization header is parsed via uudecode. uudecode determines how many bytes will be decoded by iterating over the input and checking its table. The length is then used to start decoding the string. There are no checks to ensure that the length it calculates isn't greater than the input buffer. This leads to adjacent memory being decoded as well. An attacker would not be able to retrieve the decoded data unless the Squid maintainer had configured the display of usernames on error pages.

CVSS Scores

version 3.1
Expand this section

NVD

5.9 medium
  • Attack Vector (AV)
    Network
  • Attack Complexity (AC)
    High
  • Privileges Required (PR)
    None
  • User Interaction (UI)
    None
  • Scope (S)
    Unchanged
  • Confidentiality (C)
    High
  • Integrity (I)
    None
  • Availability (A)
    None