Interpreter crash via malformed object initializer
Published Jun 10, 2021 · Updated Aug 4, 2024
Reachable assertion in the JerryScript 2.2.0 JavaScript parser allows attackers to crash the interpreter via crafted source code. The ObjectInitializer parser mishandles a string-literal property definition followed by a comma, leaves scanning unsuccessful, and then reaches the parser_parse_source assertion. Execution of attacker-controlled JavaScript is required, and the bounded consequence is process termination rather than data access or modification.
Summary
What happened
Reachable assertion in the JerryScript 2.2.0 JavaScript parser allows attackers to crash the interpreter via crafted source code. The ObjectInitializer parser mishandles a string-literal property definition followed by a comma, leaves scanning unsuccessful, and then reaches the parser_parse_source assertion. Execution of attacker-controlled JavaScript is required, and the bounded consequence is process termination rather than data access or modification.
The record
- CVE
- CVE-2020-23312
- Published
- Jun 10, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-617, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 10, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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
- GitHub issue 3824 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