Out-of-bounds Read Affecting squid:4/libecap package, versions <0:1.0.1-2.module_el8.6.0+2741+01592ae8


Severity

Recommended
0.0
medium
0
10

Based on AlmaLinux security rating.

Threat Intelligence

EPSS
15.89% (95th 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 IDSNYK-ALMALINUX8-SQUID-5617062
  • published28 May 2023
  • disclosed3 Nov 2020

Introduced: 3 Nov 2020

CVE-2019-12529  (opens in a new tab)
CWE-125  (opens 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.

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 Base Scores

version 3.1