Interpreter crash via out-of-range bytecode-part assertion
Published Jan 27, 2022 · Updated Aug 4, 2024
Reachable assertion in Cesanta MJS 2.20.0 allows attackers to crash the interpreter by executing crafted JavaScript. The mjs_bcode_part_get_by_offset function reaches an out-of-range bytecode-part index and aborts when its i < parts_cnt assertion fails. Execution of attacker-controlled JavaScript is required; the demonstrated consequence is an interpreter process abort, with no reported data disclosure or modification.
Summary
What happened
Reachable assertion in Cesanta MJS 2.20.0 allows attackers to crash the interpreter by executing crafted JavaScript. The mjs_bcode_part_get_by_offset function reaches an out-of-range bytecode-part index and aborts when its i < parts_cnt assertion fails. Execution of attacker-controlled JavaScript is required; the demonstrated consequence is an interpreter process abort, with no reported data disclosure or modification.
The record
- CVE
- CVE-2021-46508
- Published
- Jan 27, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-617, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 27, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 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 assertion-failure 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