Crash via out-of-bounds identifier read
Published May 10, 2023 · Updated Jan 27, 2025
Heap-buffer overflow in JerryScript 3.0.0 allows attackers to crash the engine by having it parse a malformed JavaScript class. lexer_compare_identifier_to_chars reads one byte beyond the source buffer while checking duplicate private class fields in malformed input. Exploitation requires the crafted script to be supplied to and parsed by a vulnerable engine; the public proof of concept demonstrates an AddressSanitizer abort, not code execution.
Summary
What happened
Heap-buffer overflow in JerryScript 3.0.0 allows attackers to crash the engine by having it parse a malformed JavaScript class. lexer_compare_identifier_to_chars reads one byte beyond the source buffer while checking duplicate private class fields in malformed input. Exploitation requires the crafted script to be supplied to and parsed by a vulnerable engine; the public proof of concept demonstrates an AddressSanitizer abort, not code execution.
The record
- CVE
- CVE-2023-31906
- Published
- May 10, 2023
- Updated
- Jan 27, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- 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.
Weakness, pattern, technique
Public exploit references
- Malformed private-class-field 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