squid: HTTP Request Splitting issue in HTTP message processing
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
Configuration 3 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Enterprise Linux 8 | |||
| squid:4-8030020200828070549.30b713e6 | cpe:/a:redhat:enterprise_linux:8 | RHSA-2020:4743 | 2020-11-04T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-2028-1 | squid3 security update |
Debian DLA |
DLA-2278-1 | squid3 security update |
Debian DSA |
DSA-4682-1 | squid security update |
EUVD |
EUVD-2019-8394 | An issue was discovered in Squid 3.x and 4.x through 4.8. It allows attackers to smuggle HTTP requests through frontend software to a Squid instance that splits the HTTP Request pipeline differently. The resulting Response messages corrupt caches (between a client and Squid) with attacker-controlled content at arbitrary URLs. Effects are isolated to software between the attacker client and Squid. There are no effects on Squid itself, nor on any upstream servers. The issue is related to a request header containing whitespace between a header name and a colon. |
Ubuntu USN |
USN-4213-1 | Squid vulnerabilities |
No CVSS v4.0
This CVE is not in the KEV list.
Exploit prediction score: 6.2% (6.200% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.