Engine crash via freed parser-list allocation
Published Jan 14, 2022 · Updated Aug 4, 2024
Use-after-free in JerryScript 2.3.0 and earlier allows remote attackers to crash an embedded engine via crafted JavaScript source. The lexer_compare_identifier_to_string function reads a parser-list allocation after parser_restore_context frees it during nested function parsing. Exploitation requires the target to parse attacker-controlled JavaScript; the demonstrated outcome is an AddressSanitizer abort, with no established data disclosure or code execution.
Summary
What happened
Use-after-free in JerryScript 2.3.0 and earlier allows remote attackers to crash an embedded engine via crafted JavaScript source. The lexer_compare_identifier_to_string function reads a parser-list allocation after parser_restore_context frees it during nested function parsing. Exploitation requires the target to parse attacker-controlled JavaScript; the demonstrated outcome is an AddressSanitizer abort, with no established data disclosure or code execution.
The record
- CVE
- CVE-2021-46170
- Published
- Jan 14, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 14, 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 lexer use-after-free 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