Skip to main content
CVE-2024-38983VulnerabilityPublished Updated

CVE-2024-38983: mini-deep-assign · n/a

Affects mini-deep-assignSource 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.9% chance of exploitation in 30 days – higher than 61% 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 30 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
npmalykoshin/mini-deep-assignpkg:npm/alykoshin/mini-deep-assignOther threatsAffected
  • =0.0.8
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-38983, organizations should first identify all instances of the mini-deep-assign library version 0.0.8 in their software supply chain and development environments. Immediate steps include: 1) Monitoring for official patches or updates from the library maintainer and applying them promptly once available. 3) Implement input validation and sanitization controls around any data passed to the _assign() method to prevent malicious prototype manipulation. 4) Employ runtime application self-protection (RASP) or web application firewalls (WAFs) with rules targeting prototype pollution attack patterns. 5) Conduct thorough code audits and static analysis to detect unsafe usage of object assignment functions. 6) Limit the privileges of applications using this library to minimize the impact of potential exploitation. 7) Educate developers about prototype pollution risks and secure coding practices in JavaScript. These targeted measures go beyond generic advice and address the specific nature of this vulnerability.

Description

Prototype Pollution in alykoshin mini-deep-assign v0.0.8 allows an attacker to execute arbitrary code or cause a Denial of Service (DoS) and cause other impacts via the _assign() method at (/lib/index.js:91)

References

Community reviews

Loading reviews…