Interpreter abort via assignment lookahead mishandling
Published Jun 10, 2021 · Updated Aug 4, 2024
Reachable assertion in JerryScript 2.2.0 allows remote attackers to abort an interpreter by submitting a crafted JavaScript expression. The expression parser mishandles assignment lookahead for a grouped left-hand-side expression, leaving its stack marker inconsistent when parser_parse_expression checks LEXER_EXPRESSION_START. Exposure requires a host application to pass remotely supplied JavaScript into an assertion-enabled build; only that process's availability is affected.
Summary
What happened
Reachable assertion in JerryScript 2.2.0 allows remote attackers to abort an interpreter by submitting a crafted JavaScript expression. The expression parser mishandles assignment lookahead for a grouped left-hand-side expression, leaving its stack marker inconsistent when parser_parse_expression checks LEXER_EXPRESSION_START. Exposure requires a host application to pass remotely supplied JavaScript into an assertion-enabled build; only that process's availability is affected.
The record
- CVE
- CVE-2020-23308
- Published
- Jun 10, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-617
- 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.
Weakness, pattern, technique
Public exploit references
- GitHub issue 3819 JavaScript test caseproof 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