CVE-2020-15811
published 2020-09-02CVE-2020-15811: 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…
PriorityP342medium6.5CVSS 3.1
AVNACLPRLUINSUCNIHAN
EPSS
4.23%
89.8th percentile
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.
Affected
18 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| canonical | ubuntu_linux | — | — |
| canonical | ubuntu_linux | — | — |
| canonical | ubuntu_linux | — | — |
| debian | debian_linux | — | — |
| debian | debian_linux | — | — |
| debian | squid | < squid 4.13-1 (bookworm) | squid 4.13-1 (bookworm) |
| fedoraproject | fedora | — | — |
| fedoraproject | fedora | — | — |
| fedoraproject | fedora | — | — |
| opensuse | leap | — | — |
| opensuse | leap | — | — |
| squid-cache | squid | < 4.13 | 4.13 |
| squid-cache | squid | >= 5.0 < 5.0.4 | 5.0.4 |
| squid | squid | >= 0 < 4.13-1 | 4.13-1 |
| squid | squid | >= 0 < 4.13-1 | 4.13-1 |
| squid | squid | >= 0 < 4.13-1 | 4.13-1 |
| squid | squid | >= 0 < 4.13-1 | 4.13-1 |
| squid | squid | >= 0 < 4.10-1ubuntu1.2 | 4.10-1ubuntu1.2 |
CVSS provenance
nvdv3.16.5MEDIUMCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
nvdv2.04.0MEDIUMAV:N/AC:L/Au:S/C:N/I:P/A:N
osv8.8HIGH
vendor_ubuntu9.9CRITICAL
vendor_debian6.5MEDIUM
vendor_redhat6.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
squid3 vulnerabilities
osv·2020-09-28·CVSS 8.8
CVE-2020-15049 [HIGH] squid3 vulnerabilities
squid3 vulnerabilities
Alex Rousskov and Amit Klein discovered that Squid incorrectly handled
certain Content-Length headers. A remote attacker could possibly use this
issue to perform an HTTP request smuggling attack, resulting in cache
poisoning. (CVE-2020-15049)
Amit Klein discovered that Squid incorrectly validated certain data. A
remote attacker could possibly use this issue to perform an HTTP request
smuggling attack, resulting in cache poisoning. (CVE-2020-15810)
Régis Leroy discovered that Squid incorrectly validated certain data. A
remote attacker could possibly use this issue to perform an HTTP request
splitting attack, resulting in cache poisoning. (CVE-2020-15811)
Lubos Uhliarik discovered that Squid incorrectly handled certain Cache
Digest response messages sent by trusted
OSV
CVE-2020-15811: An issue was discovered in Squid before 4
osv·2020-09-02·CVSS 6.5
CVE-2020-15811 [MEDIUM] CVE-2020-15811: An issue was discovered in Squid before 4
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.
OSV
squid vulnerabilities
osv·2020-08-27·CVSS 6.5
CVE-2020-15810 [MEDIUM] squid vulnerabilities
squid vulnerabilities
Amit Klein discovered that Squid incorrectly validated certain data. A
remote attacker could possibly use this issue to perform an HTTP request
smuggling attack, resulting in cache poisoning. (CVE-2020-15810)
Régis Leroy discovered that Squid incorrectly validated certain data. A
remote attacker could possibly use this issue to perform an HTTP request
splitting attack, resulting in cache poisoning. (CVE-2020-15811)
Lubos Uhliarik discovered that Squid incorrectly handled certain Cache
Digest response messages sent by trusted peers. A remote attacker could
possibly use this issue to cause Squid to consume resources, resulting in a
denial of service. (CVE-2020-24606)
Ubuntu
Squid vulnerabilities
vendor_ubuntu·2020-09-28·CVSS 9.9
CVE-2020-15049 [CRITICAL] Squid vulnerabilities
Title: Squid vulnerabilities
Summary: Several security issues were fixed in Squid.
Alex Rousskov and Amit Klein discovered that Squid incorrectly handled
certain Content-Length headers. A remote attacker could possibly use this
issue to perform an HTTP request smuggling attack, resulting in cache
poisoning. (CVE-2020-15049)
Amit Klein discovered that Squid incorrectly validated certain data. A
remote attacker could possibly use this issue to perform an HTTP request
smuggling attack, resulting in cache poisoning. (CVE-2020-15810)
Régis Leroy discovered that Squid incorrectly validated certain data. A
remote attacker could possibly use this issue to perform an HTTP request
splitting attack, resulting in cache poisoning. (CVE-2020-15811)
Lubos Uhliarik discovered that Squid incorrectly h
Ubuntu
Squid vulnerabilities
vendor_ubuntu·2020-08-27·CVSS 6.5
CVE-2020-15810 [MEDIUM] Squid vulnerabilities
Title: Squid vulnerabilities
Summary: Several security issues were fixed in Squid.
Amit Klein discovered that Squid incorrectly validated certain data. A
remote attacker could possibly use this issue to perform an HTTP request
smuggling attack, resulting in cache poisoning. (CVE-2020-15810)
Régis Leroy discovered that Squid incorrectly validated certain data. A
remote attacker could possibly use this issue to perform an HTTP request
splitting attack, resulting in cache poisoning. (CVE-2020-15811)
Lubos Uhliarik discovered that Squid incorrectly handled certain Cache
Digest response messages sent by trusted peers. A remote attacker could
possibly use this issue to cause Squid to consume resources, resulting in a
denial of service. (CVE-2020-24606)
Instructions: In general, a standard s
Red Hat
squid: HTTP Request Splitting could result in cache poisoning
vendor_redhat·2020-08-23·CVSS 6.5
CVE-2020-15811 [MEDIUM] CWE-444 squid: HTTP Request Splitting could result in cache poisoning
squid: HTTP Request Splitting could result in cache poisoning
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 ca
Debian
CVE-2020-15811: squid - An issue was discovered in Squid before 4.13 and 5.x before 5.0.4. Due to incorr...
vendor_debian·2020·CVSS 6.5
CVE-2020-15811 [MEDIUM] CVE-2020-15811: squid - An issue was discovered in Squid before 4.13 and 5.x before 5.0.4. Due to incorr...
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.
Scope: local
bookworm: resolved (fixed in 4.13-1)
bullsey
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2020-15811 squid: HTTP Request Splitting could result in cache poisoning
bugzilla·2020-08-24·CVSS 6.5
CVE-2020-15811 [MEDIUM] CVE-2020-15811 squid: HTTP Request Splitting could result in cache poisoning
CVE-2020-15811 squid: HTTP Request Splitting could result in cache poisoning
Due to incorrect data validation Squid is vulnerable to HTTP Request Splitting
attacks against HTTP and HTTPS traffic. This leads to cache poisoning.
Upstream Advisory:
https://github.com/squid-cache/squid/security/advisories/GHSA-c7p8-xqhm-49wv
Affected Versions: 2.7-3.5.28, 4.0-4.12, 5.0.1-5.0.3
Fixed Versions: 4.13, 5.0.4
Discussion:
Created squid tracking bugs for this issue:
Affects: fedora-all [bug 1871704]
---
Upstream commit:
https://github.com/squid-cache/squid/commit/fd68382860633aca92065e6c343cfd1b12b126e7
---
Mitigation:
Disable the relaxed HTTP parser in `squid.conf`:
```
relaxed_header_parser off
```
---
This issue has been addressed in the following products:
Red Hat Enterprise Linux
Bugzilla
CVE-2020-15811 squid: HTTP Request Splitting could result in cache poisoning [fedora-all]
bugzilla·2020-08-24·CVSS 6.5
CVE-2020-15811 [MEDIUM] CVE-2020-15811 squid: HTTP Request Splitting could result in cache poisoning [fedora-all]
CVE-2020-15811 squid: HTTP Request Splitting could result in cache poisoning [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple suppor
Bugzilla
CVE-2020-15811 squid: HTTP Request Splitting could result in cache poisoning [fedora-all]
bugzilla·2020-08-24·CVSS 6.5
CVE-2020-15811 [MEDIUM] CVE-2020-15811 squid: HTTP Request Splitting could result in cache poisoning [fedora-all]
CVE-2020-15811 squid: HTTP Request Splitting could result in cache poisoning [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple suppor
CWE
Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')
mitre_cwe
CWE-113 Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')
CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')
The product receives data from an HTTP agent/component (e.g., web server, proxy, browser, etc.), but it does not neutralize or incorrectly neutralizes CR and LF characters before the data is included in outgoing HTTP headers.
HTTP agents or components may include a web server, load balancer, reverse proxy, web caching proxy, application firewall, web browser, etc. Regardless of the role, they are expected to maintain coherent, consistent HTTP communication state across all components. However, including unexpected data in an HTTP header allows an attacker to specify the entirety of the HTTP message that is rendered by the client HTTP agent (e.g., web browser) or back-end HTTP agent (e.g
CWE
Incorrect Comparison
mitre_cwe
CWE-697 Incorrect Comparison
CWE-697: Incorrect Comparison
The product compares two entities in a security-relevant context, but the comparison is incorrect.
This Pillar covers several possibilities: the comparison checks one factor incorrectly; the comparison should consider multiple factors, but it does not check at least one of those factors at all; the comparison checks the wrong factor.
Modes of Introduction:
Phase: Implementation
Common Consequences:
Scope: Other. Impact: Varies by Context. When the comparison is incorrect, it may lead to resultant weaknesses.
Detection Methods:
Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to
http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00012.htmlhttp://lists.opensuse.org/opensuse-security-announce/2020-09/msg00017.htmlhttps://github.com/squid-cache/squid/security/advisories/GHSA-c7p8-xqhm-49wvhttps://lists.debian.org/debian-lts-announce/2020/10/msg00005.htmlhttps://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BE6FKUN7IGTIR2MEEMWYDT7N5EJJLZI2/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BMTFLVB7GLRF2CKGFPZ4G4R5DIIPHWI3/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HJJDI7JQFGQLVNCKMVY64LAFMKERAOK7/https://security.netapp.com/advisory/ntap-20210219-0007/https://security.netapp.com/advisory/ntap-20210226-0006/https://security.netapp.com/advisory/ntap-20210226-0007/https://usn.ubuntu.com/4477-1/https://usn.ubuntu.com/4551-1/https://www.debian.org/security/2020/dsa-4751http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00012.htmlhttp://lists.opensuse.org/opensuse-security-announce/2020-09/msg00017.htmlhttps://github.com/squid-cache/squid/security/advisories/GHSA-c7p8-xqhm-49wvhttps://lists.debian.org/debian-lts-announce/2020/10/msg00005.htmlhttps://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BE6FKUN7IGTIR2MEEMWYDT7N5EJJLZI2/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BMTFLVB7GLRF2CKGFPZ4G4R5DIIPHWI3/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HJJDI7JQFGQLVNCKMVY64LAFMKERAOK7/https://security.netapp.com/advisory/ntap-20210219-0007/https://security.netapp.com/advisory/ntap-20210226-0006/https://security.netapp.com/advisory/ntap-20210226-0007/https://usn.ubuntu.com/4477-1/https://usn.ubuntu.com/4551-1/https://www.debian.org/security/2020/dsa-4751
2020-09-02
Published