Heap over-read via crafted substring search
Published Jan 27, 2022 · Updated Aug 4, 2024
Heap-buffer over-read in Cesanta MJS 2.20.0 allows local users to read past a heap allocation by executing crafted JavaScript. During String.indexOf evaluation, mg_strstr performs a 19-byte read starting at the end of a 107-byte allocation. The attacker must cause interpreter execution of the crafted script; public evidence demonstrates a sanitizer-detected over-read but no data disclosure or code execution.
Summary
What happened
Heap-buffer over-read in Cesanta MJS 2.20.0 allows local users to read past a heap allocation by executing crafted JavaScript. During String.indexOf evaluation, mg_strstr performs a 19-byte read starting at the end of a 107-byte allocation. The attacker must cause interpreter execution of the crafted script; public evidence demonstrates a sanitizer-detected over-read but no data disclosure or code execution.
The record
- CVE
- CVE-2021-46522
- Published
- Jan 27, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- 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.
Weakness, pattern, technique
Public exploit references
- GitHub issue 196 JavaScript reproducerproof 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