Remote code execution via unchecked ESI stack growth
Published Apr 15, 2020 · Updated Aug 4, 2024
Stack buffer overflow in Squid 3.x through 3.5.28 and 4.x through 4.10 allows remote attackers to execute code via crafted ESI responses. ESIExpression::Evaluate stores parsed test-expression members in a fixed 20-element stack array, while addmember increments the stack depth without checking that bound. Exploitation requires ESI support and control of an upstream server or its transmission channel; stack protections make a proxy crash the likelier result.
Summary
What happened
Stack buffer overflow in Squid 3.x through 3.5.28 and 4.x through 4.10 allows remote attackers to execute code via crafted ESI responses. ESIExpression::Evaluate stores parsed test-expression members in a fixed 20-element stack array, while addmember increments the stack depth without checking that bound. Exploitation requires ESI support and control of an upstream server or its transmission channel; stack protections make a proxy crash the likelier result.
The record
- CVE
- CVE-2019-12519
- Published
- Apr 15, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1190
- 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.
Public exploit references
- ESI expression stack-buffer-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