Process crash via invalid array splice argument
Published Jan 27, 2022 · Updated Aug 4, 2024
Invalid memory write in Jsish 3.5.0 allows context-dependent attackers to crash the interpreter with crafted JavaScript. jsi_ArraySpliceCmd in src/jsiArray.c reports an invalid-number error for a nonnumeric splice argument but then performs an invalid memory write. Execution of the crafted script is required, and the demonstrated consequence is process termination rather than data exposure or modification.
Summary
What happened
Invalid memory write in Jsish 3.5.0 allows context-dependent attackers to crash the interpreter with crafted JavaScript. jsi_ArraySpliceCmd in src/jsiArray.c reports an invalid-number error for a nonnumeric splice argument but then performs an invalid memory write. Execution of the crafted script is required, and the demonstrated consequence is process termination rather than data exposure or modification.
The record
- CVE
- CVE-2021-46486
- Published
- Jan 27, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1204.002
- 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.
Weakness, pattern, technique
Public exploit references
- jsi_ArraySpliceCmd 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