What is CVE-2024-21505?

CVE-2024-21505 is a high-severity security vulnerability in web3-utils (npm), affecting versions >= 4.0.1, < 4.2.1. It is fixed in 4.2.1.

How severe is CVE-2024-21505?

CVE-2024-21505 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of web3-utils are affected by CVE-2024-21505?

web3-utils (npm) versions >= 4.0.1, < 4.2.1 is affected.

Is there a fix for CVE-2024-21505?

Yes. CVE-2024-21505 is fixed in 4.2.1. Upgrade to this version or later.

Is CVE-2024-21505 exploitable, and should I be worried?

Whether CVE-2024-21505 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2024-21505 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2024-21505?

Upgrade web3-utils to 4.2.1 or later.

CVE-2024-21505 in web3-utils

Q: How severe is CVE-2024-21505?

CVE-2024-21505 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of web3-utils are affected by CVE-2024-21505?

web3-utils (npm) versions >= 4.0.1, < 4.2.1 is affected.

Q: Is there a fix for CVE-2024-21505?

Yes. CVE-2024-21505 is fixed in 4.2.1. Upgrade to this version or later.

Q: Is CVE-2024-21505 exploitable, and should I be worried?

Whether CVE-2024-21505 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2024-21505 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2024-21505?

Upgrade web3-utils to 4.2.1 or later.

Summary

web3-utils Prototype Pollution vulnerability

Workarounds:

None

Impact

The mergeDeep() function in the web3-utils package has been identified for Prototype Pollution vulnerability. An attacker has the ability to modify an object's prototype, which could result in changing the behavior of all objects that inherit from the impacted prototype by providing carefully crafted input to function.

CVE-2024-21505 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.2.1); upgrading removes the vulnerable code path.

Affected versions

web3-utils (>= 4.0.1, < 4.2.1)

Security releases

web3-utils → 4.2.1 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

It has been fixed in web3-utils version 4.2.1 so all packages and apps depending on web3-utils >=4.0.1 and <=4.2.0 should upgrade to web3-utils 4.2.1.

Frequently Asked Questions

What is CVE-2024-21505? CVE-2024-21505 is a high-severity security vulnerability in web3-utils (npm), affecting versions >= 4.0.1, < 4.2.1. It is fixed in 4.2.1.
How severe is CVE-2024-21505? CVE-2024-21505 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of web3-utils are affected by CVE-2024-21505? web3-utils (npm) versions >= 4.0.1, < 4.2.1 is affected.
Is there a fix for CVE-2024-21505? Yes. CVE-2024-21505 is fixed in 4.2.1. Upgrade to this version or later.
Is CVE-2024-21505 exploitable, and should I be worried? Whether CVE-2024-21505 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2024-21505 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2024-21505? Upgrade web3-utils to 4.2.1 or later.