|Category:||Web application abuses|
|Title:||Squid Proxy Cache < 4.10 Cache Poisoning Vulnerability|
|Summary:||Squid is prone to a cache poisoning vulnerability.|
Squid is prone to a cache poisoning vulnerability.
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.
Squid versions prior to 4.10.
Update to version 4.10 or later.
Common Vulnerability Exposure (CVE) ID: CVE-2019-12520|
|Copyright||Copyright (C) 2020 Greenbone Networks GmbH|
|This is only one of 85075 vulnerability tests in our test suite. Find out more about running a complete security audit.|
To run a free test of this vulnerability against your system, register below.