Cyber Resilience

CVE-2024-57071

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.0043 36th percentile
Risk Priority 57 floored blend · peak EPSS

Summary

CVE-2024-57071 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 36th 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-57071 is a prototype pollution vulnerability in the lib.combine function of php-parser version 3.2.1. This flaw allows attackers to supply a crafted payload that pollutes the JavaScript prototype chain, leading to a Denial of Service (DoS) condition. The vulnerability is classified under CWE-1321 (Prototype Pollution) and carries a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), indicating high severity primarily due to its impact on availability.

The attack requires no authentication or user interaction, making it exploitable by unauthenticated attackers over the network with low complexity. By sending a specially crafted payload to an application using the vulnerable php-parser v3.2.1 library, attackers can trigger the prototype pollution in lib.combine, resulting in resource exhaustion or application crashes that disrupt service availability without affecting confidentiality or integrity.

Advisories reference a GitHub Gist at https://gist.github.com/tariqhawis/b56500d3a8866467ee769df7453eedaa, which likely contains proof-of-concept details for the vulnerability, though specific patch or mitigation guidance is not detailed in available information.

EU & UK References

Vulnerability Data

A prototype pollution in the lib.combine function of php-parser v3.2.1 allows attackers to cause a Denial of Service (DoS) via supplying a crafted payload.

CWE(s)

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.
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
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.
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.

finds

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

prevents

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

prevents

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

prevents

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

prevents

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

prevents

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

References