CVE-2024-57064
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2024-57064 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-57064 is a prototype pollution vulnerability (CWE-1321) in the lib.setValue function of the @syncfusion/ej2-spreadsheet npm package version 27.2.2. Published on 2025-02-05, it enables attackers to trigger a Denial of Service (DoS) by supplying a crafted payload. The vulnerability 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). The supplier disputes the issue, asserting that the lib.setValue function is not utilized.
Attackers can exploit this remotely over the network with low attack complexity, requiring no privileges, authentication, or user interaction. Exploitation involves injecting a crafted payload into the vulnerable function, resulting in high-impact disruption to availability and causing a DoS condition without affecting confidentiality or integrity.
Advisories provide limited mitigation details, with the primary reference being a GitHub Gist at https://gist.github.com/tariqhawis/1b40dc7f3836813663c871535039760e. Practitioners should verify usage of the lib.setValue function in affected deployments and consider upgrading to newer versions of @syncfusion/ej2-spreadsheet if available, while awaiting further clarification on the supplier's dispute.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-53509
Vulnerability Data
A prototype pollution in the lib.setValue function of @syncfusion/ej2-spreadsheet v27.2.2 allows attackers to cause a Denial of Service (DoS) via supplying a crafted payload. NOTE: the Supplier disputes this because they found that the lib.setValue function is not utilized.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
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.
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.
Security testing in development catches prototype-pollution flaws before release.
Secure development lifecycle mandates input validation and object-handling controls that directly prevent prototype pollution.
Application security requirements explicitly call for safeguards against unsafe object attribute manipulation.
Secure architecture principles reduce the likelihood of prototype pollution through safe design patterns.
Secure coding standards directly prohibit unsafe prototype attribute assignment and require defensive checks.
Change-management processes ensure security fixes for prototype-pollution issues are tracked and deployed.