Interpreter crash via error-reporting heap over-read
Published Feb 3, 2023 · Updated Mar 26, 2025
Heap buffer overflow in Cesanta mJS 1.26 allows local users to crash the interpreter by executing a crafted JavaScript file. While parse_literal reports an error, mjs_set_errorf dereferences a wild pointer and reads eight bytes beyond the heap buffer. Triggering the fault requires low-privilege local execution of the interpreter; the demonstrated consequence is process abort, with no reported data disclosure or modification.
Summary
What happened
Heap buffer overflow in Cesanta mJS 1.26 allows local users to crash the interpreter by executing a crafted JavaScript file. While parse_literal reports an error, mjs_set_errorf dereferences a wild pointer and reads eight bytes beyond the heap buffer. Triggering the fault requires low-privilege local execution of the interpreter; the demonstrated consequence is process abort, with no reported data disclosure or modification.
The record
- CVE
- CVE-2021-36535
- Published
- Feb 3, 2023
- Updated
- Mar 26, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 3, 2023CVE publishedPublication date reported by the CVE source.
- Mar 26, 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.
Public exploit references
- Heap_Buffer_Overflow.js 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