QID 356199

An issue was discovered in squid through 4.7 and 5.
When receiving a request, squid checks its cache to see if it can serve up a response.
It does this by making a md5 hash of the absolute url of the request.
If found, it servers the request.
The absolute url can include the decoded userinfo (username and password) for certain protocols.
This decoded info is prepended to the domain.
This allows an attacker to provide a username that has special characters to delimit the domain, and treat the rest of the url as a path or query string.
An attacker could first make a request to their domain using an encoded username, then when a request for the target domain comes in that decodes to the exact url, it will serve the attacker's html instead of the real html.
On squid servers that also act as reverse proxies, this allows an attacker to gain access to features that only reverse proxies can use, such as esi. (
( CVE-2019-12520) an issue was discovered in squid through 4.7.
When handling requests from users, squid checks its rules to see if the request should be denied.
Squid by default comes with rules to block access to the cache manager, which serves detailed server information meant for the maintainer.
This rule is implemented via url_regex.
The handler for url_regex rules url decodes an incoming request.
This allows an attacker to encode their url to bypass the url_regex check, and gain access to the blocked resource. (
( CVE-2019-12524) a flaw was found in squid.
A trusted client can directly access the cache manager information, bypassing the manager acl protection and resulting in information disclosure. (
( CVE-2022-41317)

Successful exploitation of this vulnerability could lead to a securitybreach or could affect integrity, availability, and confidentiality.