CVE-2024-24188: Jsish · Out-of-bounds Write
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 7 Feb 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubpcmacdon/jsishpkg:github/pcmacdon/jsishOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Inventory and Identification: Conduct thorough asset discovery to identify all instances of Jsish, particularly version 3.5.0, within the organization's software and embedded systems.
- Patch Management: Monitor Jsish project communications for official patches or updates addressing CVE-2024-24188 and apply them promptly once released.
- Network Segmentation: Isolate systems running Jsish from untrusted networks to reduce exposure to remote attacks.
- Application Hardening: Where possible, implement runtime protections such as address space layout randomization (ASLR), stack canaries, and control flow integrity to mitigate exploitation impact.
- Input Validation: Review and harden any interfaces that interact with Jsish scripts to minimize malicious input that could trigger the overflow.
- Monitoring and Detection: Deploy intrusion detection systems and endpoint monitoring to identify anomalous behavior indicative of exploitation attempts.
- Incident Response Preparedness: Develop and test response plans for potential exploitation scenarios involving Jsish vulnerabilities.
- Vendor Engagement: Engage with software vendors or development teams embedding Jsish to ensure awareness and coordinated remediation efforts.
Description
Jsish v3.5.0 was discovered to contain a heap-buffer-overflow in ./src/jsiUtils.c.