Engine crash via mishandled parser allocation failure
Published May 28, 2020 · Updated Aug 4, 2024
Improper exceptional-condition handling in JerryScript 2.2.0 allows attackers to crash the engine by exhausting memory during parsing. In scanner_scan_all, cleanup continues after an out-of-memory error and reaches scanner_reverse_info_list with a null pointer or asserts that no error remains. Execution requires attacker-controlled JavaScript to exhaust parser memory; the demonstrated consequence is process termination, not data access or modification.
Summary
What happened
Improper exceptional-condition handling in JerryScript 2.2.0 allows attackers to crash the engine by exhausting memory during parsing. In scanner_scan_all, cleanup continues after an out-of-memory error and reaches scanner_reverse_info_list with a null pointer or asserts that no error remains. Execution requires attacker-controlled JavaScript to exhaust parser memory; the demonstrated consequence is process termination, not data access or modification.
The record
- CVE
- CVE-2020-13649
- Published
- May 28, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, CWE-617, CWE-754, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 28, 2020CVE 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
- scanner_reverse_info_list crash reproducerproof of concept · demonstrated
- scanner_scan_all assertion 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