Out-of-bounds Read Affecting squid package, versions <7:4.11-3.module+el8.3.0+7819+eb7d4ef6


Severity

Recommended
0.0
medium
0
10

Based on Oracle Linux security rating.

Threat Intelligence

EPSS
1.09% (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 IDSNYK-ORACLE8-SQUID-2573944
  • published10 Apr 2022
  • disclosed11 Jul 2019

Introduced: 11 Jul 2019

CVE-2019-12529  (opens in a new tab)
CWE-125  (opens in a new tab)

How to fix?

Upgrade Oracle:8 squid to version 7:4.11-3.module+el8.3.0+7819+eb7d4ef6 or higher.
This issue was patched in ELSA-2020-4743.

NVD Description

Note: Versions mentioned in the description apply only to the upstream squid package and not the squid package as distributed by Oracle. See How to fix? for Oracle: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