Prototype Pollution in @intlify/shared >=9.7.0 <= 10.0.4
intlify vue-i18n
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @intlify/shared npm |
|
|
| @intlify/vue-i18n-core npm |
|
intlify vue-i18n
| Product | Affected | Fixed in |
|---|---|---|
| @intlify/shared npm |
|
|
| @intlify/vue-i18n-core npm |
|
|
| vue-i18n npm |
|
|
| petite-vue-i18n npm |
|
|
@intlify/shared is a shared library for the intlify project. 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) as 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. This issue has been addressed in versions 9.14.2, and 10.0.5. Users are advised to upgrade. There are no known workarounds for this vulnerability.
From the CVE record · GitHub_M
The lib.deepCopy function in @intlify/shared is vulnerable to prototype pollution. An attacker who can supply a payload containing an Object.prototype setter can modify the global prototype chain, causing at least denial of service; further injection impacts depend on how the application uses the library. The input does not specify whether authentication or user interaction is required.
Check applications using npm @intlify/shared, @intlify/vue-i18n-core, or vue-i18n versions >=9.7.0 <9.14.2 or >=10.0.0 <10.0.5, or petite-vue-i18n versions >=10.0.0 <10.0.5.