ubuntu-cve-2019-18678
Vulnerability from osv_ubuntu
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": [
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "squid",
"binary_version": "3.5.12-1ubuntu7.9"
},
{
"binary_name": "squid-cgi",
"binary_version": "3.5.12-1ubuntu7.9"
},
{
"binary_name": "squid-common",
"binary_version": "3.5.12-1ubuntu7.9"
},
{
"binary_name": "squid-purge",
"binary_version": "3.5.12-1ubuntu7.9"
},
{
"binary_name": "squid3",
"binary_version": "3.5.12-1ubuntu7.9"
},
{
"binary_name": "squidclient",
"binary_version": "3.5.12-1ubuntu7.9"
}
]
},
"package": {
"ecosystem": "Ubuntu:16.04:LTS",
"name": "squid3",
"purl": "pkg:deb/ubuntu/squid3@3.5.12-1ubuntu7.9?arch=source\u0026distro=xenial"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.5.12-1ubuntu7.9"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.3.8-1ubuntu16",
"3.3.8-1ubuntu17",
"3.5.12-1ubuntu6",
"3.5.12-1ubuntu7",
"3.5.12-1ubuntu7.1",
"3.5.12-1ubuntu7.2",
"3.5.12-1ubuntu7.3",
"3.5.12-1ubuntu7.4",
"3.5.12-1ubuntu7.5",
"3.5.12-1ubuntu7.6",
"3.5.12-1ubuntu7.7",
"3.5.12-1ubuntu7.8"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "squid",
"binary_version": "3.5.27-1ubuntu1.4"
},
{
"binary_name": "squid-cgi",
"binary_version": "3.5.27-1ubuntu1.4"
},
{
"binary_name": "squid-common",
"binary_version": "3.5.27-1ubuntu1.4"
},
{
"binary_name": "squid-purge",
"binary_version": "3.5.27-1ubuntu1.4"
},
{
"binary_name": "squid3",
"binary_version": "3.5.27-1ubuntu1.4"
},
{
"binary_name": "squidclient",
"binary_version": "3.5.27-1ubuntu1.4"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "squid3",
"purl": "pkg:deb/ubuntu/squid3@3.5.27-1ubuntu1.4?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.5.27-1ubuntu1.4"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.5.23-5ubuntu1",
"3.5.23-5ubuntu2",
"3.5.27-1ubuntu1",
"3.5.27-1ubuntu1.1",
"3.5.27-1ubuntu1.2",
"3.5.27-1ubuntu1.3"
]
},
{
"ecosystem_specific": {
"availability": "No subscription required",
"binaries": [
{
"binary_name": "squid",
"binary_version": "4.9-2ubuntu1"
},
{
"binary_name": "squid-cgi",
"binary_version": "4.9-2ubuntu1"
},
{
"binary_name": "squid-common",
"binary_version": "4.9-2ubuntu1"
},
{
"binary_name": "squid-purge",
"binary_version": "4.9-2ubuntu1"
},
{
"binary_name": "squid3",
"binary_version": "4.9-2ubuntu1"
},
{
"binary_name": "squidclient",
"binary_version": "4.9-2ubuntu1"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "squid",
"purl": "pkg:deb/ubuntu/squid@4.9-2ubuntu1?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.9-2ubuntu1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"4.8-1ubuntu2",
"4.8-1ubuntu3"
]
}
],
"aliases": [],
"details": "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.",
"id": "UBUNTU-CVE-2019-18678",
"modified": "2025-09-08T16:45:39Z",
"published": "2019-11-26T17:15:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2019-18678"
},
{
"type": "REPORT",
"url": "http://www.squid-cache.org/Advisories/SQUID-2019_10.txt"
},
{
"type": "ADVISORY",
"url": "https://ubuntu.com/security/notices/USN-4213-1"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2019-18678"
}
],
"related": [
"USN-4213-1"
],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2019-18678"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.