Interpreter crash via freed heap value lookup
Published Jan 27, 2022 · Updated Aug 4, 2024
Heap use-after-free in jsi_ValueLookupBase in Jsish 3.5.0 allows local users to crash the interpreter via a crafted JavaScript file. The lookup path reads one byte from a heap allocation after Jsi_DecrRefCount has freed it while resolving a bound function whose prototype was replaced. Execution of the crafted script is required, and the demonstrated consequence is interpreter termination rather than data disclosure or modification.
Summary
What happened
Heap use-after-free in jsi_ValueLookupBase in Jsish 3.5.0 allows local users to crash the interpreter via a crafted JavaScript file. The lookup path reads one byte from a heap allocation after Jsi_DecrRefCount has freed it while resolving a bound function whose prototype was replaced. Execution of the crafted script is required, and the demonstrated consequence is interpreter termination rather than data disclosure or modification.
The record
- CVE
- CVE-2021-46494
- Published
- Jan 27, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 27, 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.
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.
Public exploit references
- Jsish issue 78 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