Parser crash via post-brace character consumption
Published Feb 17, 2022 · Updated Jul 9, 2026
Reachable assertion in the JerryScript JavaScript parser allows local users to crash an embedding process via crafted source code. In lexer_expect_object_literal_id, the lexer consumes the character after a class static-block opening brace, leaving parser_parse_function_arguments with an unexpected scanner record. Execution requires an application to parse attacker-supplied JavaScript; the demonstrated assertion failure or null read aborts the process.
Summary
What happened
Reachable assertion in the JerryScript JavaScript parser allows local users to crash an embedding process via crafted source code. In lexer_expect_object_literal_id, the lexer consumes the character after a class static-block opening brace, leaving parser_parse_function_arguments with an unexpected scanner record. Execution requires an application to parse attacker-supplied JavaScript; the demonstrated assertion failure or null read aborts the process.
The record
- CVE
- CVE-2022-22901
- Published
- Feb 17, 2022
- Updated
- Jul 9, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-617, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 17, 2022CVE publishedPublication date reported by the CVE source.
- Jul 9, 2026Record 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
- Upstream issue 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