Process crash via parser heap out-of-bounds read
Published May 10, 2023 · Updated Jan 28, 2025
Heap-buffer overflow in JerryScript 3.0.0 allows local users to crash the engine by supplying crafted JavaScript for parsing. In parser_parse_function_statement at js-parser-statm.c:696, malformed static-block syntax drives a two-byte read four bytes before an eight-byte heap allocation. Exploitation requires the engine to parse attacker-controlled source with user interaction; the public reproducer demonstrates an abort, not code execution.
Summary
What happened
Heap-buffer overflow in JerryScript 3.0.0 allows local users to crash the engine by supplying crafted JavaScript for parsing. In parser_parse_function_statement at js-parser-statm.c:696, malformed static-block syntax drives a two-byte read four bytes before an eight-byte heap allocation. Exploitation requires the engine to parse attacker-controlled source with user interaction; the public reproducer demonstrates an abort, not code execution.
The record
- CVE
- CVE-2023-31910
- Published
- May 10, 2023
- Updated
- Jan 28, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 10, 2023CVE publishedPublication date reported by the CVE source.
- Jan 28, 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
- poc.js parser crash reproducerproof 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