CVE-2019-18678
Published: 26 November 2019
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.
Priority
Status
Package | Release | Status |
---|---|---|
squid Launchpad, Ubuntu, Debian |
bionic |
Does not exist
|
disco |
Released
(4.4-1ubuntu2.3)
|
|
eoan |
Released
(4.8-1ubuntu2.1)
|
|
focal |
Released
(4.9-2ubuntu1)
|
|
groovy |
Released
(4.9-2ubuntu1)
|
|
hirsute |
Released
(4.9-2ubuntu1)
|
|
trusty |
Does not exist
|
|
upstream |
Released
(4.9-1)
|
|
xenial |
Does not exist
|
|
Patches: upstream: http://www.squid-cache.org/Versions/v4/changesets/squid-4-671ba97abe929156dc4c717ee52ad22fba0f7443.patch |
||
squid3 Launchpad, Ubuntu, Debian |
bionic |
Released
(3.5.27-1ubuntu1.4)
|
disco |
Does not exist
|
|
eoan |
Does not exist
|
|
focal |
Does not exist
|
|
groovy |
Does not exist
|
|
hirsute |
Does not exist
|
|
trusty |
Does not exist
|
|
upstream |
Needs triage
|
|
xenial |
Released
(3.5.12-1ubuntu7.9)
|
Severity score breakdown
Parameter | Value |
---|---|
Base score | 5.3 |
Attack vector | Network |
Attack complexity | Low |
Privileges required | None |
User interaction | None |
Scope | Unchanged |
Confidentiality | None |
Integrity impact | Low |
Availability impact | None |
Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |