Interpreter crash via bound RegExp heap overwrite
Published Jan 25, 2022 · Updated Aug 4, 2024
Heap buffer overflow in Jsish 3.5.0 allows context-dependent attackers to crash the interpreter through crafted JavaScript. RegExp_constructor writes an eight-byte value before a heap allocation when a bound RegExp constructor is invoked with crafted arguments. Execution requires a user to run the malicious script, and the documented consequence is an interpreter crash rather than data access or modification.
Summary
What happened
Heap buffer overflow in Jsish 3.5.0 allows context-dependent attackers to crash the interpreter through crafted JavaScript. RegExp_constructor writes an eight-byte value before a heap allocation when a bound RegExp constructor is invoked with crafted arguments. Execution requires a user to run the malicious script, and the documented consequence is an interpreter crash rather than data access or modification.
The record
- CVE
- CVE-2021-46477
- Published
- Jan 25, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- 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.
Public exploit references
- Bound RegExp constructor heap-overflow 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