Proxy crash via off-by-one ESI stack write
Published Apr 15, 2020 · Updated Aug 4, 2024
Denial of service in Squid 3.x through 3.5.28, 4.x through 4.10, and 5.0.1 allows remote attackers to crash the proxy via ESI responses. ESIContext::addStackElement accepts an eleventh ESIElement because its depth check permits index 10 in the ten-entry parserState.stack array, overwriting the adjacent stackdepth member. Exploitation requires ESI support and control of an upstream server or its transmission channel; successful processing terminates the proxy and interrupts service for its clients.
Summary
What happened
Denial of service in Squid 3.x through 3.5.28, 4.x through 4.10, and 5.0.1 allows remote attackers to crash the proxy via ESI responses. ESIContext::addStackElement accepts an eleventh ESIElement because its depth check permits index 10 in the ten-entry parserState.stack array, overwriting the adjacent stackdepth member. Exploitation requires ESI support and control of an upstream server or its transmission channel; successful processing terminates the proxy and interrupts service for its clients.
The record
- CVE
- CVE-2019-12521
- Published
- Apr 15, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, CWE-193, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 15, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- ESIContext parserState.stack overflow reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo