Service crash via malformed script cleanup
Published Jan 2, 2024 · Updated Jun 3, 2025
Denial of service in Cesanta mJS 2.20.0 allows remote attackers to crash an embedding process via a crafted JavaScript file. During error cleanup, mjs_destroy passes the json_visited_stack buffer to mbuf_free, where the published proof of concept reaches a segmentation fault. No authentication or user interaction is required, and the demonstrated consequence is process termination.
Summary
What happened
Denial of service in Cesanta mJS 2.20.0 allows remote attackers to crash an embedding process via a crafted JavaScript file. During error cleanup, mjs_destroy passes the json_visited_stack buffer to mbuf_free, where the published proof of concept reaches a segmentation fault. No authentication or user interaction is required, and the demonstrated consequence is process termination.
The record
- CVE
- CVE-2023-49553
- Published
- Jan 2, 2024
- Updated
- Jun 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 2, 2024CVE publishedPublication date reported by the CVE source.
- Jun 3, 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_destroy segmentation-fault 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