CVE-2019-18678
published 2019-11-26CVE-2019-18678: 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…
PriorityP340medium5.3CVSS 3.1
AVNACLPRNUINSUCNILAN
EPSS
10.93%
95.3th percentile
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.
Affected
14 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| canonical | ubuntu_linux | — | — |
| canonical | ubuntu_linux | — | — |
| canonical | ubuntu_linux | — | — |
| canonical | ubuntu_linux | — | — |
| debian | debian_linux | — | — |
| debian | squid | < squid 4.9-1 (bookworm) | squid 4.9-1 (bookworm) |
| fedoraproject | fedora | — | — |
| fedoraproject | fedora | — | — |
| squid-cache | squid | 3.0 – 3.5.28 | — |
| squid-cache | squid | 4.0 – 4.8 | — |
| squid | squid | >= 0 < 4.9-1 | 4.9-1 |
| squid | squid | >= 0 < 4.9-1 | 4.9-1 |
| squid | squid | >= 0 < 4.9-1 | 4.9-1 |
| squid | squid | >= 0 < 4.9-1 | 4.9-1 |
CVSS provenance
nvdv3.15.3MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:N/I:P/A:N
osv9.1CRITICAL
vendor_ubuntu9.1CRITICAL
vendor_debian5.3MEDIUM
vendor_redhat5.3MEDIUM
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.
Ubuntu
Squid vulnerabilities
vendor_ubuntu·2019-12-04·CVSS 9.1
CVE-2019-12523 [CRITICAL] Squid vulnerabilities
Title: Squid vulnerabilities
Summary: Several security issues were fixed in Squid.
Jeriko One and Kristoffer Danielsson discovered that Squid incorrectly
handled certain URN requests. A remote attacker could possibly use this
issue to bypass access checks and access restricted servers. This issue was
only addressed in Ubuntu 19.04 and Ubuntu 19.10. (CVE-2019-12523)
Jeriko One discovered that Squid incorrectly handed URN responses. A remote
attacker could use this issue to cause Squid to crash, resulting in a
denial of service, or possibly execute arbitrary code. (CVE-2019-12526)
Alex Rousskov discovered that Squid incorrectly handled certain strings. A
remote attacker could possibly use this issue to cause Squid to crash,
resulting in a denial of service. This issue only affected Ubunt
Red Hat
squid: HTTP Request Splitting issue in HTTP message processing
vendor_redhat·2019-11-05·CVSS 5.3
CVE-2019-18678 [MEDIUM] CWE-20 squid: HTTP Request Splitting issue in HTTP message processing
squid: HTTP Request Splitting issue in HTTP message processing
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.
Package: squid (Red Hat Enterprise Linux 5) - Not affected
Package: squid (Red Hat Enterprise Linux 6) - Out of support scope
Package: squid34 (Red Hat Enterprise Linux
Debian
CVE-2019-18678: squid - An issue was discovered in Squid 3.x and 4.x through 4.8. It allows attackers to...
vendor_debian·2019·CVSS 5.3
CVE-2019-18678 [MEDIUM] CVE-2019-18678: squid - An issue was discovered in Squid 3.x and 4.x through 4.8. It allows attackers to...
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.
Scope: local
bookworm: resolved (fixed in 4.9-1)
bullseye: resolved (fixed in 4.9-1)
forky: resolved (fixed in 4.9-1)
sid: resolved (fixed in 4.9-1)
trixie: resolved (fixed in 4.9-1)
GHSA
GHSA-jvgf-c7c2-w98p: An issue was discovered in Squid 3
ghsa_unreviewed·2022-05-24
CVE-2019-18678 [MEDIUM] GHSA-jvgf-c7c2-w98p: An issue was discovered in Squid 3
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.
OSV
squid, squid3 vulnerabilities
osv·2019-12-04·CVSS 9.1
CVE-2019-12523 [CRITICAL] squid, squid3 vulnerabilities
squid, squid3 vulnerabilities
Jeriko One and Kristoffer Danielsson discovered that Squid incorrectly
handled certain URN requests. A remote attacker could possibly use this
issue to bypass access checks and access restricted servers. This issue was
only addressed in Ubuntu 19.04 and Ubuntu 19.10. (CVE-2019-12523)
Jeriko One discovered that Squid incorrectly handed URN responses. A remote
attacker could use this issue to cause Squid to crash, resulting in a
denial of service, or possibly execute arbitrary code. (CVE-2019-12526)
Alex Rousskov discovered that Squid incorrectly handled certain strings. A
remote attacker could possibly use this issue to cause Squid to crash,
resulting in a denial of service. This issue only affected Ubuntu 19.04.
(CVE-2019-12854)
Jeriko One and Kristoffer D
OSV
CVE-2019-18678: An issue was discovered in Squid 3
osv·2019-11-26·CVSS 5.3
CVE-2019-18678 [MEDIUM] CVE-2019-18678: An issue was discovered in Squid 3
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.
No detection rules found.
No public exploits indexed.
HackerOne
HTTP Smuggling multiple issues in Squid 3.x & squid 4.x
hackerone·2021-08-26·CVSS 5.3
[MEDIUM] HTTP Smuggling multiple issues in Squid 3.x & squid 4.x
HTTP Smuggling multiple issues in Squid 3.x & squid 4.x
Hello, as can be seen on a recent public security update by Squid I reported several smuggling issues.
If you want some background on impact of Smuggling issues You can check the current works of James Keetle or my own previous published works.
* https://www.youtube.com/watch?v=upEMlJeU_Ik HTTP Desync Attacks: Smashing Into The Cell Next Door - James Kettle
* https://www.youtube.com/watch?v=dVU9i5PsMPY DEF CON 24 - regilero - Hiding Wookiees in HTTP: HTTP smuggling
But I'm quite sure that the recent additions of Smuggling tools in Burp suite is making Smuggling impacts issues more easy to understand now.
# CVE-2019-18678
* http://www.squid-cache.org/Advisories/SQUID-2019_10.txt
current score (5 / 5.3) available at :
* https://ww
Bugzilla
CVE-2019-18678 squid: HTTP Request Splitting issue in HTTP message processing
bugzilla·2019-11-08·CVSS 5.3
CVE-2019-18678 [MEDIUM] CVE-2019-18678 squid: HTTP Request Splitting issue in HTTP message processing
CVE-2019-18678 squid: HTTP Request Splitting issue in HTTP message processing
Due to incorrect message parsing Squid is vulnerable to an HTTP request splitting issue. This issue allows attackers to smuggle HTTP requests through frontend software to a Squid which splits the HTTP Request pipeline differently. The resulting Response messages corrupt caches between client and Squid with attacker controlled content at arbitrary URLs.
References:
http://www.squid-cache.org/Advisories/SQUID-2019_10.txt
Discussion:
Created squid tracking bugs for this issue:
Affects: fedora-all [bug 1770350]
---
Upstream patch: http://www.squid-cache.org/Versions/v4/changesets/squid-4-671ba97abe929156dc4c717ee52ad22fba0f7443.patch
---
External References:
http://www.squid-cache.org/Advisories/SQUID-2019
Bugzilla
CVE-2019-18678 squid: HTTP Request Splitting issue in HTTP message processing [fedora-all]
bugzilla·2019-11-08·CVSS 5.3
CVE-2019-18678 [MEDIUM] CVE-2019-18678 squid: HTTP Request Splitting issue in HTTP message processing [fedora-all]
CVE-2019-18678 squid: HTTP Request Splitting issue in HTTP message processing [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 suppo
http://www.squid-cache.org/Advisories/SQUID-2019_10.txthttp://www.squid-cache.org/Versions/v4/changesets/squid-4-671ba97abe929156dc4c717ee52ad22fba0f7443.patchhttps://bugzilla.suse.com/show_bug.cgi?id=1156323https://github.com/squid-cache/squid/pull/445https://lists.debian.org/debian-lts-announce/2019/12/msg00011.htmlhttps://lists.debian.org/debian-lts-announce/2020/07/msg00009.htmlhttps://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/MTM74TU2BSLT5B3H4F3UDW53672NVLMC/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UEMOYTMCCFWK5NOXSXEIH5D2VGWVXR67/https://security.gentoo.org/glsa/202003-34https://usn.ubuntu.com/4213-1/https://www.debian.org/security/2020/dsa-4682http://www.squid-cache.org/Advisories/SQUID-2019_10.txthttp://www.squid-cache.org/Versions/v4/changesets/squid-4-671ba97abe929156dc4c717ee52ad22fba0f7443.patchhttps://bugzilla.suse.com/show_bug.cgi?id=1156323https://github.com/squid-cache/squid/pull/445https://lists.debian.org/debian-lts-announce/2019/12/msg00011.htmlhttps://lists.debian.org/debian-lts-announce/2020/07/msg00009.htmlhttps://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/MTM74TU2BSLT5B3H4F3UDW53672NVLMC/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UEMOYTMCCFWK5NOXSXEIH5D2VGWVXR67/https://security.gentoo.org/glsa/202003-34https://usn.ubuntu.com/4213-1/https://www.debian.org/security/2020/dsa-4682
2019-11-26
Published