Interpreter crash via out-of-bounds heap read
Published Jan 25, 2022 · Updated Aug 4, 2024
Out-of-bounds read in Jsish 3.5.0 allows local users to crash the interpreter by executing a crafted JavaScript file. In jsiEvalCodeSub in src/jsiEval.c, evaluation of a strict-mode function that assigns to eval reads eight bytes before an allocated heap buffer. Execution of attacker-controlled JavaScript and user interaction are required; the demonstrated consequence is interpreter termination, not code execution.
Summary
What happened
Out-of-bounds read in Jsish 3.5.0 allows local users to crash the interpreter by executing a crafted JavaScript file. In jsiEvalCodeSub in src/jsiEval.c, evaluation of a strict-mode function that assigns to eval reads eight bytes before an allocated heap buffer. Execution of attacker-controlled JavaScript and user interaction are required; the demonstrated consequence is interpreter termination, not code execution.
The record
- CVE
- CVE-2021-46474
- Published
- Jan 25, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 25, 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.
Weakness, pattern, technique
Public exploit references
- GitHub issue 57 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