Invalid memory read via stale for-in index
Published Jun 20, 2022 · Updated Aug 4, 2024
Heap use-after-free in JerryScript 2.4.0 allows local users to trigger an invalid read by executing crafted JavaScript during typed-array sorting. In vm_loop, an abrupt Proxy has result enters cleanup without saving the current for-in collection index, so cleanup releases a string that later property lookup compares. Execution of attacker-controlled JavaScript is required; the public test produces an AddressSanitizer abort, while code execution is not demonstrated.
Summary
What happened
Heap use-after-free in JerryScript 2.4.0 allows local users to trigger an invalid read by executing crafted JavaScript during typed-array sorting. In vm_loop, an abrupt Proxy has result enters cleanup without saving the current for-in collection index, so cleanup releases a string that later property lookup compares. Execution of attacker-controlled JavaScript is required; the public test produces an AddressSanitizer abort, while code execution is not demonstrated.
The record
- CVE
- CVE-2021-41682
- Published
- Jun 20, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 20, 2022CVE 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 4747 reproduction 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