Interpreter crash via freed-memory write
Published Feb 7, 2024 · Updated Jun 20, 2025
Use-after-free in SplitChar in Jsish 3.5.0 allows attackers to crash the interpreter by executing a crafted JavaScript split operation. SplitChar writes eight bytes through a pointer to memory already freed by Jsi_ObjFree while processing an oversized repeated string. The published proof of concept requires execution of attacker-controlled JavaScript and demonstrates an AddressSanitizer abort; code execution is not demonstrated.
Summary
What happened
Use-after-free in SplitChar in Jsish 3.5.0 allows attackers to crash the interpreter by executing a crafted JavaScript split operation. SplitChar writes eight bytes through a pointer to memory already freed by Jsi_ObjFree while processing an oversized repeated string. The published proof of concept requires execution of attacker-controlled JavaScript and demonstrates an AddressSanitizer abort; code execution is not demonstrated.
The record
- CVE
- CVE-2024-24189
- Published
- Feb 7, 2024
- Updated
- Jun 20, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 7, 2024CVE publishedPublication date reported by the CVE source.
- Jun 20, 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.
Weakness, pattern, technique
Public exploit references
- Jsish SplitChar heap-use-after-free 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