VDB

CVE-2020-15811

CVE-2020-15811 PUBLISHED

Reported by mitre · Published September 2, 2020

An issue was discovered in Squid before 4.13 and 5.x before 5.0.4. Due to incorrect data validation, HTTP Request Splitting attacks may succeed against HTTP and HTTPS traffic. This leads to cache poisoning. This allows any client, including browser scripts, to bypass local security and poison the browser cache and any downstream caches with content from an arbitrary source. Squid uses a string search instead of parsing the Transfer-Encoding header to find chunked encoding. This allows an attacker to hide a second request inside Transfer-Encoding: it is interpreted by Squid as chunked and split out into a second request delivered upstream. Squid will then deliver two distinct responses to the client, corrupting any downstream caches.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
squidsquid-cache5.0.4, 4.13
squidUbuntu:20.04:LTS4.10-1ubuntu1.2

Affected products

VendorProductVersions
n/an/an/a
n/an/a*
amazon:2squid-sysvinit0
amazon:2squid-migration-script0
amazon:2squid0
alpinesquid0, 0

Timeline

  • Sep 2, 2020 CVE Published
  • Apr 14, 2021 EPSS Score (30 in total, the first dated here)
  • Aug 26, 2021 PoC Published
  • Mar 6, 2026 Distribution Patch (6 in total, the first dated here)
  • Mar 6, 2026 Security Advisory (10 in total, the first dated here)
  • Sep 4, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2020-15811
vulnetix vdb fixes CVE-2020-15811

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2020-15811/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›