Vue I18n Prototype Pollution in `handleFlatJson`
intlify vue-i18n
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @intlify/message-resolver npm |
|
|
| @intlify/vue-i18n-core npm |
|
intlify vue-i18n
| Product | Affected | Fixed in |
|---|---|---|
| @intlify/message-resolver npm |
|
|
| @intlify/vue-i18n-core npm |
|
9.14.310.0.611.1.2| petite-vue-i18n npm |
|
|
| vue-i18n npm |
|
|
| @intlify/core-base npm |
|
|
| @intlify/core npm |
|
|
Vue I18n is the internationalization plugin for Vue.js. @intlify/message-resolver and @intlify/vue-i18n-core are vulnerable to Prototype Pollution through the entry function: handleFlatJson. 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) a 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.
From the CVE record · GitHub_M
The handleFlatJson function in @intlify/message-resolver and @intlify/vue-i18n-core is vulnerable to prototype pollution. If an attacker can supply a payload containing an Object.prototype setter, they can modify the global prototype chain, causing at least a denial of service. Other injection-based impacts depend on how the application uses the polluted properties; the input does not specify whether authentication or user interaction is required.
Teams using affected npm versions of @intlify/message-resolver, @intlify/core-base, or @intlify/core (>=9.1.0 <9.1.11); @intlify/vue-i18n-core or vue-i18n (>=9.2.0 <9.14.3 or >=9.1.0 <9.14.3, respectively, or >=10.0.0-alpha.1 <10.0.6 or >=11.0.0-beta.0 <11.1.2); or petite-vue-i18n (>=10.0.0 <10.0.6 or >=11.0.0-beta.0 <11.1.2) should check their dependencies.