Engine crash via out-of-bounds parser read
Published May 10, 2023 · Updated Jan 27, 2025
Heap-buffer overflow in JerryScript 3.0.0 allows context-dependent attackers to crash the engine with crafted JavaScript source. The scanner_literal_is_created function reads two bytes beyond a heap allocation while parser_parse_var_statement processes crafted class syntax. Execution requires a user or embedding application to parse attacker-controlled JavaScript; the public reproducer triggers an AddressSanitizer abort.
Summary
What happened
Heap-buffer overflow in JerryScript 3.0.0 allows context-dependent attackers to crash the engine with crafted JavaScript source. The scanner_literal_is_created function reads two bytes beyond a heap allocation while parser_parse_var_statement processes crafted class syntax. Execution requires a user or embedding application to parse attacker-controlled JavaScript; the public reproducer triggers an AddressSanitizer abort.
The record
- CVE
- CVE-2023-31907
- Published
- May 10, 2023
- Updated
- Jan 27, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 10, 2023CVE publishedPublication date reported by the CVE source.
- Jan 27, 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
- JerryScript issue 5073 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