Interpreter crash via crafted load filename
Published Jan 27, 2022 · Updated Aug 4, 2024
Denial of service in Cesanta mJS 2.20.0 allows local users to crash the interpreter by executing a crafted JavaScript file. The built-in load() path sends an attacker-controlled filename through mjs_exec_file to cs_read_file, where a null-pointer read triggers SIGSEGV. Execution requires a user or embedding application to run the malicious script; the demonstrated consequence is process termination only.
Summary
What happened
Denial of service in Cesanta mJS 2.20.0 allows local users to crash the interpreter by executing a crafted JavaScript file. The built-in load() path sends an attacker-controlled filename through mjs_exec_file to cs_read_file, where a null-pointer read triggers SIGSEGV. Execution requires a user or embedding application to run the malicious script; the demonstrated consequence is process termination only.
The record
- CVE
- CVE-2021-46543
- 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
- mJS crafted load-string 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