xst crash via crafted prototype assignment
Published Jan 20, 2022 · Updated Aug 4, 2024
A segmentation fault in Moddable SDK 11.5.0 allows local users to crash xst by executing a crafted JavaScript file. xst processes a prototype assignment involving a setInterval result, then reaches an invalid read and apparent wild jump in _fini during error finalization. Exploitation requires local execution of the crafted script, and the demonstrated consequence is termination of the xst process.
Summary
What happened
A segmentation fault in Moddable SDK 11.5.0 allows local users to crash xst by executing a crafted JavaScript file. xst processes a prototype assignment involving a setInterval result, then reaches an invalid read and apparent wild jump in _fini during error finalization. Exploitation requires local execution of the crafted script, and the demonstrated consequence is termination of the xst process.
The record
- CVE
- CVE-2021-46329
- Published
- Jan 20, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 20, 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.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
- poc.js crash reproducerproof 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