Process crash via NULL pointer dereference
Published Jul 26, 2022 · Updated Aug 3, 2024
NULL pointer dereference in Cesanta mjs allows local users to crash the JavaScript engine by opening a crafted script file. The mjs_next() iterator in mjs.c dereferences a NULL pointer while processing the malformed script, producing a segmentation fault. Exploitation requires user interaction to open the file and interrupts only the hosting mjs process; no data disclosure or modification is reported.
Summary
What happened
NULL pointer dereference in Cesanta mjs allows local users to crash the JavaScript engine by opening a crafted script file. The mjs_next() iterator in mjs.c dereferences a NULL pointer while processing the malformed script, producing a segmentation fault. Exploitation requires user interaction to open the file and interrupts only the hosting mjs process; no data disclosure or modification is reported.
The record
- CVE
- CVE-2021-33446
- Published
- Jul 26, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1204.002
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jul 26, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- mjs_next NULL-pointer-dereference 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