Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-38984: n/a

0
Critical
VulnerabilityCVE-2024-38984cvecve-2024-38984
Published: Tue Jul 30 2024 (07/30/2024, 00:00:00 UTC)
Source: CVE Database V5

Description

CVE-2024-38984 is a critical prototype pollution vulnerability in the json-override library version 0. 2. 0. It allows unauthenticated remote attackers to manipulate the __proto__ property, leading to arbitrary code execution or denial of service (DoS). The vulnerability has a CVSS score of 9. 8, indicating high severity with network attack vector, no privileges or user interaction required, and full impact on confidentiality, integrity, and availability. No known exploits in the wild have been reported yet. Organizations using json-override 0. 2. 0 in their software stacks should urgently assess their exposure and apply mitigations.

AI-Powered Analysis

AILast updated: 02/26/2026, 05:42:40 UTC

Technical Analysis

CVE-2024-38984 is a prototype pollution vulnerability identified in the json-override library version 0.2.0, a JavaScript utility used to override JSON objects. Prototype pollution occurs when an attacker can manipulate the __proto__ property of JavaScript objects, thereby altering the prototype chain and injecting or modifying properties on all objects. This can lead to severe consequences such as arbitrary code execution or denial of service (DoS). In this case, the vulnerability allows attackers to remotely and without authentication exploit the __proto__ property to execute malicious code or crash applications relying on json-override. The vulnerability has a CVSS 3.1 score of 9.8, reflecting its critical nature with network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and full impact on confidentiality, integrity, and availability (C:H/I:H/A:H). The weakness is classified under CWE-1321, which relates to improper handling of prototype pollution. Although no public exploits have been reported yet, the severity and ease of exploitation make this a significant threat for any Node.js applications using this library. The lack of a patch link indicates that a fix may not yet be publicly available, increasing the urgency for mitigation and monitoring.

Potential Impact

The impact of CVE-2024-38984 is substantial for organizations worldwide that use the json-override library in their JavaScript or Node.js applications. Successful exploitation can lead to arbitrary code execution, allowing attackers to take full control of affected systems, steal sensitive data, or disrupt services. The denial of service impact can cause application crashes, leading to downtime and loss of availability. Given the network-based attack vector and no requirement for authentication or user interaction, attackers can remotely exploit vulnerable systems at scale. This poses a risk to web applications, backend services, and any software components relying on json-override 0.2.0. The critical severity rating underscores the potential for widespread damage, including data breaches, service outages, and reputational harm. Organizations with automated deployment pipelines or supply chain dependencies on this library are particularly vulnerable. The absence of known exploits in the wild currently provides a window for proactive defense, but the risk of imminent exploitation remains high.

Mitigation Recommendations

To mitigate CVE-2024-38984, organizations should immediately audit their software dependencies to identify usage of json-override version 0.2.0. Until an official patch is released, consider the following specific actions: 1) Remove or replace json-override with alternative libraries that do not have prototype pollution vulnerabilities. 2) Implement input validation and sanitization to block or filter out payloads attempting to manipulate the __proto__ property. 3) Employ runtime security tools such as Node.js security modules or application firewalls that detect and prevent prototype pollution attacks. 4) Monitor application logs and network traffic for suspicious activity indicative of prototype pollution exploitation attempts. 5) Apply strict Content Security Policies (CSP) and sandboxing where applicable to limit the impact of potential code execution. 6) Stay updated with vendor advisories and apply patches promptly once available. 7) Conduct security testing, including fuzzing and static analysis, focusing on prototype pollution vectors. These targeted mitigations go beyond generic advice by focusing on the unique aspects of prototype pollution and the specific library involved.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
mitre
Date Reserved
2024-06-21T00:00:00.000Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6c7eb7ef31ef0b565021

Added to database: 2/25/2026, 9:41:18 PM

Last enriched: 2/26/2026, 5:42:40 AM

Last updated: 2/26/2026, 7:59:42 AM

Views: 1

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats