Engine crash via reachable parser assertion
Published Jun 14, 2023 · Updated Jan 2, 2025
Reachable assertion in JerryScript 3.0.0 allows attackers to crash the JavaScript engine by supplying crafted JavaScript source. The parser_parse_for_statement_start function applies a fatal assertion to a right-parenthesis token reached while parsing the crafted class-and-loop sequence. The trigger must reach an embedding application's script-parsing path; the demonstrated consequence is a process abort, not code execution.
Summary
What happened
Reachable assertion in JerryScript 3.0.0 allows attackers to crash the JavaScript engine by supplying crafted JavaScript source. The parser_parse_for_statement_start function applies a fatal assertion to a right-parenthesis token reached while parsing the crafted class-and-loop sequence. The trigger must reach an embedding application's script-parsing path; the demonstrated consequence is a process abort, not code execution.
The record
- CVE
- CVE-2023-34868
- Published
- Jun 14, 2023
- Updated
- Jan 2, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-617, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 14, 2023CVE publishedPublication date reported by the CVE source.
- Jan 2, 2025Record 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
- Issue 5083 JavaScript 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