CVE-2016-2570
Last modified
CVE-2016-2570 is a vulnerability of currently unknown severity. The Edge Side Includes (ESI) parser in Squid 3.x before 3.5.15 and 4.x before 4.0.7 does not check buffer limits during XML parsing, which allows remote HTTP servers to cause a denial of service (assertion failure and daemon exit) via a crafted XML document, related to esi/CustomParser.cc and esi/CustomParser.h.. EPSS estimates a 9.03% chance of exploitation in the next 30 days.
Description
The Edge Side Includes (ESI) parser in Squid 3.x before 3.5.15 and 4.x before 4.0.7 does not check buffer limits during XML parsing, which allows remote HTTP servers to cause a denial of service (assertion failure and daemon exit) via a crafted XML document, related to esi/CustomParser.cc and esi/CustomParser.h.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Squid-Cache | Squid | 3.0 |
| Squid-Cache | Squid | 3.0.stable1 |
| Squid-Cache | Squid | 3.0.stable2 |
| Squid-Cache | Squid | 3.0.stable3 |
| Squid-Cache | Squid | 3.0.stable4 |
| Squid-Cache | Squid | 3.0.stable5 |
| Squid-Cache | Squid | 3.0.stable6 |
| Squid-Cache | Squid | 3.0.stable7 |
| Squid-Cache | Squid | 3.0.stable8 |
| Squid-Cache | Squid | 3.0.stable9 |
| Squid-Cache | Squid | 3.0.stable10 |
| Squid-Cache | Squid | 3.0.stable11 |
| Squid-Cache | Squid | 3.0.stable12 |
| Squid-Cache | Squid | 3.0.stable13 |
| Squid-Cache | Squid | 3.0.stable14 |
| Squid-Cache | Squid | 3.0.stable15 |
| Squid-Cache | Squid | 3.0.stable16 |
| Squid-Cache | Squid | 3.0.stable17 |
| Squid-Cache | Squid | 3.0.stable18 |
| Squid-Cache | Squid | 3.0.stable19 |
| Squid-Cache | Squid | 3.0.stable20 |
| Squid-Cache | Squid | 3.0.stable21 |
| Squid-Cache | Squid | 3.0.stable22 |
| Squid-Cache | Squid | 3.0.stable23 |
| Squid-Cache | Squid | 3.0.stable24 |
| Squid-Cache | Squid | 3.0.stable25 |
| Squid-Cache | Squid | 3.1 |
| Squid-Cache | Squid | 3.1.0.1 |
| Squid-Cache | Squid | 3.1.0.2 |
| Squid-Cache | Squid | 3.1.0.3 |
| Squid-Cache | Squid | 3.1.0.4 |
| Squid-Cache | Squid | 3.1.0.5 |
| Squid-Cache | Squid | 3.1.0.6 |
| Squid-Cache | Squid | 3.1.0.7 |
| Squid-Cache | Squid | 3.1.0.8 |
| Squid-Cache | Squid | 3.1.0.9 |
| Squid-Cache | Squid | 3.1.0.10 |
| Squid-Cache | Squid | 3.1.0.11 |
| Squid-Cache | Squid | 3.1.0.12 |
| Squid-Cache | Squid | 3.1.0.13 |
| Squid-Cache | Squid | 3.1.0.14 |
| Squid-Cache | Squid | 3.1.0.15 |
| Squid-Cache | Squid | 3.1.0.16 |
| Squid-Cache | Squid | 3.1.0.17 |
| Squid-Cache | Squid | 3.1.0.18 |
| Squid-Cache | Squid | 3.1.1 |
| Squid-Cache | Squid | 3.1.2 |
| Squid-Cache | Squid | 3.1.3 |
| Squid-Cache | Squid | 3.1.4 |
| Squid-Cache | Squid | 3.1.5 |
Showing 50 of 133 affected configurations. See NVD for the full list.
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-2570?
How severe is CVE-2016-2570?
How do I fix CVE-2016-2570?
Are you affected by CVE-2016-2570?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
