Squid 2.7 to 2.7.STABLE5, 3.0 to 3.0.STABLE12, and 3.1 to 3.1.0.4 allows remote attackers to cause a denial of service…
No fixed version listed yet.Check the vendor advisory. References ↓
The flaw is in Squid's HTTP message handling, affecting the 2.7 through 2.7.STABLE5, 3.0 through 3.0.STABLE12, and 3.1 through 3.1.0.4 release lines, specifically in the HttpMsg.c and HttpStatusLine.c components. A remote attacker who can send an HTTP request containing an invalid version number can trigger a reachable assertion in one of these components, causing a denial of service; no authentication or user interaction is indicated.
Official description · CVE.org
Squid 2.7 to 2.7.STABLE5, 3.0 to 3.0.STABLE12, and 3.1 to 3.1.0.4 allows remote attackers to cause a denial of service via an HTTP request with an invalid version number, which triggers a reachable assertion in (1) HttpMsg.c and (2) HttpStatusLine.c.
- Exploited
- Not confirmed
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
Public exploit code (Exploit-DB) appeared 1 day after disclosure. No confirmed exploitation is recorded.
- Disclosedday 0
- Public exploit codeExploit-DB+1 day