Release Date: | 2019-11-26 |
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.
See more information about CVE-2019-18678 from MITRE CVE dictionary and NIST NVD
NOTE: The following CVSS v3.0 metrics and score provided are preliminary and subject to review.
Base Score: | 5.3 | Base Metrics: | AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
Access Vector: | Network | Attack Complexity: | Low |
Privileges Required: | None | User Interaction: | None |
Scope: | Unchanged | Confidentiality Impact: | None |
Integrity Impact: | Low | Availability Impact: | None |
Platform | Errata | Release Date |
Oracle Linux version 8 (libecap) | ELSA-2020-4743 | 2020-11-10 |
Oracle Linux version 8 (squid) | ELSA-2020-4743 | 2020-11-10 |
This page is generated automatically and has not been checked for errors or omissions. For clarification or corrections please contact the Oracle Linux ULN team