Interpreter crash via pre-buffer byte write
Published Jan 27, 2022 · Updated Aug 4, 2024
Heap buffer overflow in Cesanta MJS 2.20.0 allows attackers to crash the interpreter via execution of a crafted JavaScript file. The to_json_or_debug routine handles an error from malformed chained JSON.stringify calls by writing one byte before its allocated heap region. Exploitation requires the crafted script to run locally with user interaction; the published proof demonstrates an abort, not arbitrary code execution.
Summary
What happened
Heap buffer overflow in Cesanta MJS 2.20.0 allows attackers to crash the interpreter via execution of a crafted JavaScript file. The to_json_or_debug routine handles an error from malformed chained JSON.stringify calls by writing one byte before its allocated heap region. Exploitation requires the crafted script to run locally with user interaction; the published proof demonstrates an abort, not arbitrary code execution.
The record
- CVE
- CVE-2021-46523
- Published
- Jan 27, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- 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
- poc.js heap-buffer-overflow 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