Interpreter crash via crafted JavaScript file
Published Jul 26, 2022 · Updated Aug 3, 2024
Stack buffer overflow in Cesanta mJS before 2.20.0 allows local users to crash the interpreter by supplying a crafted JavaScript file. The public report identifies mjs_execute() in mjs.c as the fault locus but does not disclose the operation that mishandles the crafted input before stack exhaustion. Opening and executing the file locally is required; the demonstrated consequence is interpreter termination, with no published confidentiality or integrity impact.
Summary
What happened
Stack buffer overflow in Cesanta mJS before 2.20.0 allows local users to crash the interpreter by supplying a crafted JavaScript file. The public report identifies mjs_execute() in mjs.c as the fault locus but does not disclose the operation that mishandles the crafted input before stack exhaustion. Opening and executing the file locally is required; the demonstrated consequence is interpreter termination, with no published confidentiality or integrity impact.
The record
- CVE
- CVE-2021-33443
- Published
- Jul 26, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
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
- Crafted JavaScript file 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