GHSA-9r9m-ffp6-9x4v vue-i18n has cross-site scripting vulnerability with prototype pollution

• npm @intlify/core-base: >= 9.3.0, < 9.14.2 → fixed in 9.14.2 • npm vue-i18n: >= 9.3.0, < 9.14.2 → fixed in 9.14.2 • npm @intlify/core: >= 9.3.0, < 9.14.2 → fixed in 9.14.2 • npm @intlify/vue-i18n-core: >= 9.3.0, < 9.14.2 → fixed in 9.14.2 • npm petite-vue-i18n: >= 10.0.0, < 10.0.5 → fixed in 10.0.5 • npm @intlify/core-base: >= 10.0.0, < 10.0.5 → fixed in 10.0.5 • npm vue-i18n: >= 10.0.0, < 10.0.5 → fixed in 10.0.5 • npm @intlify/core: >= 10.0.0, < 10.0.5 → fixed in 10.0.5 • npm @intlify/vue-i18n-core: >= 10.0.0, < 10.0.5 → fixed in 10.0.5

Vulnerability type XSS Description vue-i18n can be passed locale messages to `createI18n` or `useI18n`. we can then translate them using `t` and `$t`. vue-i18n has its own syntax for local messages, and uses a message compiler to generate AST. In order to maximize the performance of the translation function, vue-i18n uses bundler plugins such as `@intlify/unplugin-vue-i18n` and bulder to convert the AST in advance when building the application. By using that AST as the locale message, it is no longer necessary to compile, and it is possible to translate using the AST. The AST generated by the message compiler has special properties for each node in the AST tree to maximize performance. In the PoC example below, it is a `static` property, but that is just one of the optimizations. About details of special properties, see https://github.com/intlify/vue-i18n/blob/master/packages/message-compiler/src/nodes.ts In general, the locale messages of vue-i18n are optimized during production builds using `@intlify/unplugin-vue-i18n`, so there is always a property that is attached during optimization like this time. But if you are using a locale message AST in development mode or your own, there is a possibility of XSS if a third party injects. Reproduce (PoC) ```html vue-i18n XSS /** • Prototype pollution vulnerability with `Object.prototype`. • The 'static' property is part of the optimized AST generated by the vue-i18n message compiler. • About details of special properties, see https://github.com/intlify/vue-i18n/blob/master/packages/message-compiler/src/nodes.ts * • In general, the locale messages of vue-i18n are optimized during production builds using `@intlify/unplugin-vue-i18n`, • so there is always a property that is attached during optimization like this time. • But if you are using a locale message AST in development or your own, there is a possibility of XSS if a third party injects prototype pollution code. */ Object.defineProperty(Object.prototype, 'static', { configurable: true, get() { alert('prototype polluted!') return 'prototype pollution' } }) {{ t('hello') }} const { createApp } = Vue const { createI18n, useI18n } = VueI18n // AST style locale message, which build by `@intlify/unplugin-vue-i18n` const en = { hello: { type: 0, body: { items: [ { type: 3, value: 'hello world!' } ] } } } const i18n = createI18n({ legacy: false, locale: 'en', messages: { en } }) const app = createApp({ setup() { const { t } = useI18n() return { t } } }) app.use(i18n) app.mount('#app') ``` Workarounds Before v10.0.0, we can work around this vulnerability by using the regular compilation (`jit: false` of `@intlify/unplugin-vue-i18n` plugin configuration) way instead of jit compilation. • jit compilation: https://vue-i18n.intlify.dev/guide/advanced/optimization.html#jit-compilation • bundler plugin option: https://github.com/intlify/bundle-tools/tree/main/packages/unplugin-vue-i18n#jitcompilation References • Simillar case: Vue 2 XSS vulnerability with prototype pollution