Engine crash via unchecked recursive construction
Published Jun 20, 2022 · Updated Aug 4, 2024
Stack overflow in JerryScript 2.4.0 allows context-dependent attackers to crash the engine by executing recursive JavaScript. The VM repeatedly constructs Foo and resolves its lexical environment without stopping recursive constructor calls before the native stack is exhausted. Execution of crafted JavaScript is required, and the demonstrated consequence is an AddressSanitizer-detected process abort.
Summary
What happened
Stack overflow in JerryScript 2.4.0 allows context-dependent attackers to crash the engine by executing recursive JavaScript. The VM repeatedly constructs Foo and resolves its lexical environment without stopping recursive constructor calls before the native stack is exhausted. Execution of crafted JavaScript is required, and the demonstrated consequence is an AddressSanitizer-detected process abort.
The record
- CVE
- CVE-2021-41683
- Published
- Jun 20, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 20, 2022CVE 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
- Recursive-constructor stack-overflow 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