Local memory corruption via BooleanConstructor heap overflow
Published Jan 25, 2022 · Updated Aug 4, 2024
Heap buffer overflow in Jsish 3.5.0 allows local users to corrupt memory by executing a crafted JavaScript program. BooleanConstructor performs a four-byte write six bytes beyond a 42-byte heap allocation when crafted code invokes a bound Boolean constructor during an Array.every callback. The interpreter must execute attacker-supplied JavaScript, and the published proof of concept produces an AddressSanitizer-detected abort.
Summary
What happened
Heap buffer overflow in Jsish 3.5.0 allows local users to corrupt memory by executing a crafted JavaScript program. BooleanConstructor performs a four-byte write six bytes beyond a 42-byte heap allocation when crafted code invokes a bound Boolean constructor during an Array.every callback. The interpreter must execute attacker-supplied JavaScript, and the published proof of concept produces an AddressSanitizer-detected abort.
The record
- CVE
- CVE-2021-46483
- Published
- Jan 25, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- 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
- BooleanConstructor 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