Application crash via late bound-function initialization
Published Jun 10, 2021 · Updated Aug 3, 2024
Invalid memory access in JerryScript 2.4.0 allows context-dependent attackers to crash an embedding application with crafted JavaScript. The bound-function path initializes its length property too late, allowing Proxy getter reentrancy to leave an invalid internal value that ecma_deref_bigint later reads during cleanup. Exploitation requires a host application to execute attacker-controlled JavaScript, and the demonstrated consequence is a process crash rather than data disclosure or modification.
Summary
What happened
Invalid memory access in JerryScript 2.4.0 allows context-dependent attackers to crash an embedding application with crafted JavaScript. The bound-function path initializes its length property too late, allowing Proxy getter reentrancy to leave an invalid internal value that ecma_deref_bigint later reads during cleanup. Exploitation requires a host application to execute attacker-controlled JavaScript, and the demonstrated consequence is a process crash rather than data disclosure or modification.
The record
- CVE
- CVE-2021-26198
- Published
- Jun 10, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 10, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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
- Upstream issue 4402 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