CVE-2019-18678Not scoredCWE-444

CVE-2019-18678: Squid-Cache vulnerability

Squid-Cache · Squid

Vendor fix available · Affected: Squid-Cache · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

6.2%probability of exploitation in the next 30 days

93rd percentile

050100

Higher than 93% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

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.

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Inconsistent Interpretation of HTTP Requests · Injection and Smuggling
Vendor: Squid-Cache
Published: November 2019
Band: Possible (1 to 10%), November 2019

CoverageNo articles yet

No CyberSIXT article names CVE-2019-18678 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.