Cyber Resilience

CVE-2024-57066

Published
05 February 2025
Modified
15 April 2026
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0048 39th percentile
Risk Priority 58 floored blend · peak EPSS

Summary

CVE-2024-57066 is a high-severity Prototype Pollution (CWE-1321) vulnerability. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 39th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-57066 is a prototype pollution vulnerability in the lib.deep function of the @ndhoule/defaults npm package version 2.0.1. This flaw allows attackers to manipulate object prototypes by supplying a crafted payload, leading to a Denial of Service (DoS) condition. The vulnerability is classified under CWE-1321 (Prototype Pollution) with a CVSS v3.1 base score of 7.5, reflecting high severity due to its impact on availability.

Remote attackers can exploit this vulnerability over the network with low complexity, requiring no privileges, authentication, or user interaction (AV:N/AC:L/PR:N/UI:N). By injecting a malicious payload into the lib.deep function, an attacker can pollute the prototype chain, potentially crashing the application or rendering it unresponsive, resulting in high availability impact (A:H) without affecting confidentiality or integrity.

Advisories point to a GitHub Gist for further details on the vulnerability: https://gist.github.com/tariqhawis/8ee7327cc8b78df738cd32505cbbbd44. No specific patches or mitigations are detailed in the provided CVE information.

EU & UK References

Vulnerability Data

A prototype pollution in the lib.deep function of @ndhoule/defaults v2.0.1 allows attackers to cause a Denial of Service (DoS) via supplying a crafted payload.

CWE(s)
CWE-1321

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1565 Data Manipulation Impact
Adversaries may insert, delete, or manipulate data in order to influence external outcomes or hide activity, thus threatening the integrity of the data.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-33672Shared CWE-1321
CVE-2024-39018Shared CWE-1321
CVE-2026-46510Shared CWE-1321
CVE-2024-36578Shared CWE-1321
CVE-2019-0230Shared CWE-1321
CVE-2026-34621Shared CWE-1321
CVE-2024-36580Shared CWE-1321
CVE-2025-54803Shared CWE-1321
CVE-2025-3193Shared CWE-1321
CVE-2024-30564Shared CWE-1321

Affected Assets

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V15.3.6

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and safe property assignment to prevent prototype pollution.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches prototype-pollution flaws before release.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and object-handling controls that directly prevent prototype pollution.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for safeguards against unsafe object attribute manipulation.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce the likelihood of prototype pollution through safe design patterns.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly prohibit unsafe prototype attribute assignment and require defensive checks.

A.8.32 Change management partial match
prevents

Change-management processes ensure security fixes for prototype-pollution issues are tracked and deployed.

References