Engine crash via malformed JSON pointer dereference
Published Jan 2, 2024 · Updated Sep 6, 2024
Improper input validation in Cesanta mjs 2.20.0 allows remote attackers to crash the engine by parsing crafted JSON input. The mjs_op_json_parse function in mjs.c processes malformed JSON into an invalid high-address pointer and dereferences it during a read, producing a segmentation fault. The input must reach JSON.parse through an embedding application's network-facing path; successful exploitation aborts the hosting process only.
Summary
What happened
Improper input validation in Cesanta mjs 2.20.0 allows remote attackers to crash the engine by parsing crafted JSON input. The mjs_op_json_parse function in mjs.c processes malformed JSON into an invalid high-address pointer and dereferences it during a read, producing a segmentation fault. The input must reach JSON.parse through an embedding application's network-facing path; successful exploitation aborts the hosting process only.
The record
- CVE
- CVE-2023-49551
- Published
- Jan 2, 2024
- Updated
- Sep 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 2, 2024CVE publishedPublication date reported by the CVE source.
- Sep 6, 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.
Public exploit references
- mjs JSON.parse crash 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