Interpreter crash via null-address write
Published May 9, 2023 · Updated Jan 29, 2025
Memory corruption in Cesanta MJS 1.26 allows local users to crash the interpreter by executing a crafted JavaScript file. In mjs_execute in mjs.c, the crafted input reaches line 9320 and triggers a write through a null address, producing an AddressSanitizer segmentation fault. Execution of the attacker-supplied file with low-privilege local access is required, and the demonstrated consequence is process termination rather than code execution.
Summary
What happened
Memory corruption in Cesanta MJS 1.26 allows local users to crash the interpreter by executing a crafted JavaScript file. In mjs_execute in mjs.c, the crafted input reaches line 9320 and triggers a write through a null address, producing an AddressSanitizer segmentation fault. Execution of the attacker-supplied file with low-privilege local access is required, and the demonstrated consequence is process termination rather than code execution.
The record
- CVE
- CVE-2023-30088
- Published
- May 9, 2023
- Updated
- Jan 29, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-119, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 9, 2023CVE publishedPublication date reported by the CVE source.
- Jan 29, 2025Record 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
- mjs_execute invalid-memory-read 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