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.
References
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: mitre
Published: 2019-11-26T16:15:42
Updated: 2020-07-10T23:06:15
Reserved: 2019-11-04T00:00:00
Link: CVE-2019-18678
JSON object: View
NVD Information
Status : Modified
Published: 2019-11-26T17:15:12.983
Modified: 2023-11-07T03:06:53.910
Link: CVE-2019-18678
JSON object: View
Redhat Information
No data.
CWE