CVE-2019-12520Not scoredCWE-20

CVE-2019-12520: Squid-Cache vulnerability

Squid-Cache · Squid

Vendor fix available · Affected: Squid-Cache · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

3.9%probability of exploitation in the next 30 days

90th percentile

050100

Higher than 90% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

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.

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Improper Input Validation · Input Validation and Logic
Vendor: Squid-Cache
Published: April 2020
Band: Possible (1 to 10%), April 2020
Bounty reports: 1 disclosed on HackerOne

Disclosed bug bounty reports about CVE-2019-12520

The reports on HackerOne that name this CVE, with HackerOne's own outcome. Titles and metadata only.

Cache PoisoningInternet Bug Bounty · 2021 · high severityValid

CoverageNo articles yet

No CyberSIXT article names CVE-2019-12520 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.