Engine abort via reused private-identifier literal
Published Jan 20, 2022 · Updated Aug 4, 2024
Reachable assertion in JerryScript 3.0.0 allows context-dependent attackers to crash the engine by supplying crafted JavaScript. During private-identifier resolution, the parser reuses a literal object instead of constructing a new one, causing parser_list_get to exhaust its page list and fail the page_p != NULL assertion. Execution of the crafted script is required, and a successful trigger aborts the JerryScript process without reported confidentiality or integrity impact.
Summary
What happened
Reachable assertion in JerryScript 3.0.0 allows context-dependent attackers to crash the engine by supplying crafted JavaScript. During private-identifier resolution, the parser reuses a literal object instead of constructing a new one, causing parser_list_get to exhaust its page list and fail the page_p != NULL assertion. Execution of the crafted script is required, and a successful trigger aborts the JerryScript process without reported confidentiality or integrity impact.
The record
- CVE
- CVE-2021-46337
- Published
- Jan 20, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-617, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 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
- JerryScript private-reference assertion 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