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.
History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published: 2019-11-26T16:15:42

Updated: 2024-08-05T02:02:38.289Z

Reserved: 2019-11-04T00:00:00

Link: CVE-2019-18678

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2019-11-26T17:15:12.983

Modified: 2024-11-21T04:33:30.973

Link: CVE-2019-18678

cve-icon Redhat

Severity : Moderate

Publid Date: 2019-11-05T00:00:00Z

Links: CVE-2019-18678 - Bugzilla