Interpreter crash via oversized split operation
Published Feb 7, 2024 · Updated Jun 9, 2025
Heap buffer overflow in Jsish 3.5.0 allows attackers to crash the interpreter by evaluating crafted JavaScript split operations. In SplitChar, strcpy writes a 52,953,081-byte string immediately past the end of a 100,000,000-byte heap allocation after an oversized repeat-and-split expression. The interpreter must evaluate attacker-controlled JavaScript; the published proof of concept ends in an AddressSanitizer abort, while code execution is not demonstrated.
Summary
What happened
Heap buffer overflow in Jsish 3.5.0 allows attackers to crash the interpreter by evaluating crafted JavaScript split operations. In SplitChar, strcpy writes a 52,953,081-byte string immediately past the end of a 100,000,000-byte heap allocation after an oversized repeat-and-split expression. The interpreter must evaluate attacker-controlled JavaScript; the published proof of concept ends in an AddressSanitizer abort, while code execution is not demonstrated.
The record
- CVE
- CVE-2024-24188
- Published
- Feb 7, 2024
- Updated
- Jun 9, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 7, 2024CVE publishedPublication date reported by the CVE source.
- Jun 9, 2025Record 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
- JavaScript split-operation 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