Engine crash via reentrant slice endpoint conversion
Published Jul 3, 2023 · Updated Nov 25, 2024
Memory-safety failure in JerryScript 2.3.0 allows attackers to crash the engine with a crafted Array.prototype.slice end argument. The operation converts the end argument through valueOf after caching the array length; reentrant truncation leaves its copy loop reading released values. Exploitation requires an embedding application to execute attacker-controlled JavaScript; the upstream reproducer demonstrates a crash, not code execution.
Summary
What happened
Memory-safety failure in JerryScript 2.3.0 allows attackers to crash the engine with a crafted Array.prototype.slice end argument. The operation converts the end argument through valueOf after caching the array length; reentrant truncation leaves its copy loop reading released values. Exploitation requires an embedding application to execute attacker-controlled JavaScript; the upstream reproducer demonstrates a crash, not code execution.
The record
- CVE
- CVE-2020-22597
- Published
- Jul 3, 2023
- Updated
- Nov 25, 2024
- Vendor
- JerryScript Project
- Product
- JerryScript
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 3, 2023CVE publishedPublication date reported by the CVE source.
- Nov 25, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.3.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Array.slice reentrant-truncation 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