Medium severity · published Jul 11, 2019
CVE-2019-12529
An issue was discovered in Squid 2.x through 2.7.STABLE9, 3.x through 3.5.28, and 4.x through 4.7
5.9
CVSS
8.1%
EPSS
No
On KEV
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.
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Confidentiality
High
Integrity
None
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)8.1% · higher than 95% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
DL
Debian Linux · Debian
8.0; 9.0; 10.0 · source: NVD
FE
Fedora · Fedoraproject
29 · source: NVD
LE
Leap · Opensuse
15.0; 15.1 · source: NVD
SQ
Squid · Squid-cache
2.0 before 2.7; 3.0 through 3.5.28; 4.0 through 4.7; 2.7; 2.7; 2.7; +6 more · source: NVD
UL
Ubuntu Linux · Canonical
12.04; 16.04; 18.04; 19.04 · source: NVD