Process crash via unchecked Proxy recursion
Published May 26, 2020 · Updated Aug 4, 2024
Stack exhaustion in JerryScript 2.2.0 allows remote attackers to crash an embedding process through crafted Proxy object operations. Self-referential Proxy prototype chains make ecma_proxy_object_get and ecma_proxy_object_set recurse without enforcing the engine's stack limit. The host must execute attacker-controlled JavaScript with Proxy support; exhaustion terminates the affected process without reported data access or modification.
Summary
What happened
Stack exhaustion in JerryScript 2.2.0 allows remote attackers to crash an embedding process through crafted Proxy object operations. Self-referential Proxy prototype chains make ecma_proxy_object_get and ecma_proxy_object_set recurse without enforcing the engine's stack limit. The host must execute attacker-controlled JavaScript with Proxy support; exhaustion terminates the affected process without reported data access or modification.
The record
- CVE
- CVE-2020-13623
- Published
- May 26, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 26, 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
- Upstream self-referential Proxy proof of conceptproof 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