Interpreter crash via near-null memory read
Published Jan 27, 2022 · Updated Aug 4, 2024
Invalid memory access in Cesanta mJS 2.20.0 allows context-dependent attackers to crash the interpreter via crafted JavaScript. The mjs_bcode_insert_offset routine in src/mjs_bcode.c reads through a near-null address while processing the crafted script, producing a segmentation fault. Execution of attacker-supplied JavaScript by a victim is required, and the demonstrated consequence is process termination without reported confidentiality or integrity impact.
Summary
What happened
Invalid memory access in Cesanta mJS 2.20.0 allows context-dependent attackers to crash the interpreter via crafted JavaScript. The mjs_bcode_insert_offset routine in src/mjs_bcode.c reads through a near-null address while processing the crafted script, producing a segmentation fault. Execution of attacker-supplied JavaScript by a victim is required, and the demonstrated consequence is process termination without reported confidentiality or integrity impact.
The record
- CVE
- CVE-2021-46556
- Published
- Jan 27, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- Unavailable
- 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
No sourced classifications are available.
Public exploit references
- GitHub issue 227 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