CVE-2016-2572
UnknownEPSS 10.24%
Last modified
CVE-2016-2572 is a vulnerability of currently unknown severity. http.cc in Squid 4.x before 4.0.7 relies on the HTTP status code after a response-parsing failure, which allows remote HTTP servers to cause a denial of service (assertion failure and daemon exit) via a malformed response.. EPSS estimates a 10.24% chance of exploitation in the next 30 days.
Description
http.cc in Squid 4.x before 4.0.7 relies on the HTTP status code after a response-parsing failure, which allows remote HTTP servers to cause a denial of service (assertion failure and daemon exit) via a malformed response.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Squid-Cache | Squid | 4.0.1 |
| Squid-Cache | Squid | 4.0.2 |
| Squid-Cache | Squid | 4.0.3 |
| Squid-Cache | Squid | 4.0.4 |
| Squid-Cache | Squid | 4.0.5 |
| Squid-Cache | Squid | 4.0.6 |
References
- http://www.squid-cache.org/Advisories/SQUID-2016_2.txtVendor Advisory
- http://www.squid-cache.org/Advisories/SQUID-2016_2.txtVendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2016-2572?
http.cc in Squid 4.x before 4.0.7 relies on the HTTP status code after a response-parsing failure, which allows remote HTTP servers to cause a denial of service (assertion failure and daemon exit) via a malformed response.
How severe is CVE-2016-2572?
Severity scoring for CVE-2016-2572 is pending analysis. The EPSS model estimates a 10.24% probability of exploitation in the next 30 days.
How do I fix CVE-2016-2572?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
Are you affected by CVE-2016-2572?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST