CVE-2019-12529: Medium severity Squid-Cache Squid vulnerability
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.
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2019-12529?
The severity of CVE-2019-12529 is medium.
How does CVE-2019-12529 affect Squid?
CVE-2019-12529 affects Squid versions 2.x through 2.7.STABLE9, 3.x through 3.5.28, and 4.x through 4.7.
How is Proxy-Authorization header parsed in Squid?
Proxy-Authorization header is parsed via uudecode in Squid.
What is the recommended remedy for CVE-2019-12529 on Ubuntu?
The recommended remedy for CVE-2019-12529 on Ubuntu is to update to the latest version of squid or squid3.
Where can I find more information about CVE-2019-12529?
You can find more information about CVE-2019-12529 at the official website of Squid and the security announcement links provided.