Improper memory read via garbage-collection race
Published Jun 15, 2020 · Updated Aug 4, 2024
JerryScript 2.2.0 memory-safety flaw allows attackers to trigger improper memory reads via crafted JavaScript Map key/value operations. The container operation can trigger garbage collection after processing a key but before processing its value, leaving a stale object pointer that ecma_gc_set_object_visited dereferences. Execution requires the vulnerable interpreter to process attacker-controlled script; observed outcomes include crashes or information disclosure, with no evidence of integrity impact.
Summary
What happened
JerryScript 2.2.0 memory-safety flaw allows attackers to trigger improper memory reads via crafted JavaScript Map key/value operations. The container operation can trigger garbage collection after processing a key but before processing its value, leaving a stale object pointer that ecma_gc_set_object_visited dereferences. Execution requires the vulnerable interpreter to process attacker-controlled script; observed outcomes include crashes or information disclosure, with no evidence of integrity impact.
The record
- CVE
- CVE-2020-14163
- Published
- Jun 15, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-119
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 15, 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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 #3804 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