Skip to main content
CVE-2024-38993VulnerabilityPublished Updated

CVE-2024-38993: jsonic-next · n/a

Affects jsonic-nextSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 58% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Jul 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
npmjsonic-nextpkg:npm/jsonic-nextOther threatsAffected
  • =2.12.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-38993, organizations should first identify all instances where jsonic-next v2.12.1 is used, including transitive dependencies in their software supply chain. Until an official patch is released, consider the following specific actions: 1) Implement strict input validation and sanitization to prevent malicious payloads from reaching the vulnerable 'empty' function. 2) Use runtime application self-protection (RASP) or Web Application Firewalls (WAFs) configured to detect and block prototype pollution attack patterns. 3) Employ dependency scanning tools to monitor for updates or patches to jsonic-next and apply them promptly once available. 4) Isolate or sandbox components that rely on jsonic-next to limit the blast radius of potential exploitation. 5) Conduct code reviews focusing on usage of the 'empty' function and refactor or replace it with safer alternatives if feasible. 6) Monitor logs and network traffic for anomalous behavior indicative of prototype pollution or code injection attempts. 7) Educate development teams about prototype pollution risks and secure coding practices to prevent similar vulnerabilities in the future.

Description

rjrodger jsonic-next v2.12.1 was discovered to contain a prototype pollution via the function empty. This vulnerability allows attackers to execute arbitrary code or cause a Denial of Service (DoS) via injecting arbitrary properties.

References

Community reviews

Loading reviews…