|Description||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.|
|Source||CVE (at NVD; CERT, LWN, oss-sec, fulldisc, bugtraq, EDB, Metasploit, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, Mageia, GitHub code/issues, web search, more)|
|References||DLA-1858-1, DLA-2278-1, DSA-4507-1, ELA-271-1|
Vulnerable and fixed packages
The table below lists information on source packages.
|bullseye (security), bullseye||4.13-10+deb11u2||fixed|
|squid3 (PTS)||jessie, jessie (lts)||3.5.23-5+deb8u6||fixed|
|stretch (lts), stretch||3.5.23-5+deb9u9||fixed|
The information below is based on the following data on fixed versions.
Squid 4: http://www.squid-cache.org/Versions/v4/changesets/squid-4-dd46b5417809647f561d8a5e0e74c3aacd235258.patch