Interpreter crash via recursive error logging
Published Jan 27, 2022 · Updated Aug 4, 2024
Uncontrolled recursion in Jsi_LogMsg in Jsish 3.5.0 allows local users to crash the interpreter by executing a crafted script. While reporting an invalid WebSocket object, Jsi_LogMsg repeatedly invokes Jsi_ValueToString, which reenters Jsi_LogMsg until the process stack is exhausted. Execution of attacker-supplied JavaScript is required, and the demonstrated consequence is termination of the affected interpreter process.
Summary
What happened
Uncontrolled recursion in Jsi_LogMsg in Jsish 3.5.0 allows local users to crash the interpreter by executing a crafted script. While reporting an invalid WebSocket object, Jsi_LogMsg repeatedly invokes Jsi_ValueToString, which reenters Jsi_LogMsg until the process stack is exhausted. Execution of attacker-supplied JavaScript is required, and the demonstrated consequence is termination of the affected interpreter process.
The record
- CVE
- CVE-2021-46507
- Published
- Jan 27, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-674, 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.
Weakness, pattern, technique
Public exploit references
- Jsish Jsi_LogMsg stack-overflow 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