CVE-2024-24189
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJsish v3.5.0 (commit 42c694c) was discovered to contain a use-after-free via the SplitChar at ./src/jsiUtils.c.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceJsish v3.5.0 contains a use-after-free vulnerability in the SplitChar function in src/jsiUtils.c. The vulnerability allows memory to be accessed after being freed, potentially leading to arbitrary code execution or denial of service. This is a critical memory corruption issue in a JavaScript interpreter that can likely be exploited remotely without authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 3.5.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Detect if Jsish is installedRun 'jsish --version' or check for jsish binary in common paths like /usr/bin/jsish, /usr/local/bin/jsish. Also check if jsish is available via 'which jsish'Affected if Jsish is not found in the system - not affected. If found, proceed to version check.
-
Identify installed Jsish versionExecute 'jsish --version' and parse the output to obtain the exact version numberAffected if Version equals 3.5.0 exactly - continue to next check. Versions lower or higher than 3.5.0 are not affected by this specific CVE.
-
Confirm SplitChar function usageReview application code or scripts that use Jsish to determine if the SplitChar function from the Jsi Utils module is being called. Check for invocations like Jsi_ObjSplit or usage of string splitting features that internally call SplitCharAffected if Running Jsish 3.5.0 AND executing code that triggers the SplitChar function - likely affected. If SplitChar is not used, the vulnerability may not be triggered.
Environment is affected if Jsish version 3.5.0 is installed AND code using the SplitChar function (or features that internally invoke it) is being executed.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Jsish to a version containing the patch for this vulnerability. If no patched version exists, implement bounds checking and ensure proper memory lifecycle management in the SplitChar function to prevent premature freeing or post-free access of pointers.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24189 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-24189 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data