Engine crash via unterminated Unicode escape
Published Jun 10, 2021 · Updated Aug 4, 2024
Heap out-of-bounds access in JerryScript 2.2.0 allows attackers to crash the engine with a truncated Unicode regular expression. The re_parse_char_escape routine in re-parser.c reads beyond the heap buffer because Unicode-mode parsing omits end-of-string checks before consuming escape characters. Execution requires an application to pass attacker-controlled JavaScript containing the malformed RegExp to an ES2015 Unicode-enabled JerryScript engine.
Summary
What happened
Heap out-of-bounds access in JerryScript 2.2.0 allows attackers to crash the engine with a truncated Unicode regular expression. The re_parse_char_escape routine in re-parser.c reads beyond the heap buffer because Unicode-mode parsing omits end-of-string checks before consuming escape characters. Execution requires an application to pass attacker-controlled JavaScript containing the malformed RegExp to an ES2015 Unicode-enabled JerryScript engine.
The record
- CVE
- CVE-2020-23323
- Published
- Jun 10, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- 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
- JerryScript issue 3871 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