Skip to main content
VulnerabilityPublished Updated

CVE-2024-39013: 2o3t-utility · Prototype Pollution

Affects 2o3t-utilitySource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 55% 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
npm2o3t-utilitypkg:npm/2o3t-utilityOther threatsAffected
  • =0.1.2
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-39013, organizations should immediately assess their use of 2o3t-utility v0.1.2 and related versions. If possible, discontinue or isolate the vulnerable utility until a patch is released. Employ strict input validation and sanitization to prevent injection of malicious properties into objects. Implement runtime application self-protection (RASP) or JavaScript security tools that detect and block prototype pollution attempts. Monitor application logs and network traffic for unusual behavior indicative of exploitation attempts. Restrict network access to services using the vulnerable utility, limiting exposure to trusted internal networks. Stay informed about vendor updates or patches and apply them promptly once available. Additionally, conduct code reviews and security testing focused on prototype pollution vectors in custom code that interacts with 2o3t-utility. Employ defense-in-depth strategies such as sandboxing and privilege separation to minimize potential damage from exploitation.

Description

2o3t-utility v0.1.2 was discovered to contain a prototype pollution via the function extend. This vulnerability allows attackers to execute arbitrary code or cause a Denial of Service (DoS) via injecting arbitrary properties.

References

Community reviews

Loading reviews…