Release Date: | 2019-07-11 |
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.
See more information about CVE-2019-12529 from MITRE CVE dictionary and NIST NVD
NOTE: The following CVSS v3.0 metrics and score provided are preliminary and subject to review.
Base Score: | 5.9 | Base Metrics: | AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
Access Vector: | Network | Attack Complexity: | High |
Privileges Required: | None | User Interaction: | None |
Scope: | Unchanged | Confidentiality Impact: | High |
Integrity Impact: | None | Availability Impact: | None |
Platform | Errata | Release Date |
Oracle Linux version 8 (libecap) | ELSA-2020-4743 | 2020-11-10 |
Oracle Linux version 8 (squid) | ELSA-2020-4743 | 2020-11-10 |
This page is generated automatically and has not been checked for errors or omissions. For clarification or corrections please contact the Oracle Linux ULN team