Vue I18n HTML injection in mixed list and named interpolation
intlify vue-i18n
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| vue-i18n npm |
|
|
| @intlify/core npm |
|
intlify vue-i18n
| Product | Affected | Fixed in |
|---|---|---|
| vue-i18n npm |
|
|
| @intlify/core npm |
|
|
| @intlify/core-base npm |
|
|
| petite-vue-i18n npm |
|
|
| @intlify/vue-i18n-core npm |
|
|
Vue I18n is the internationalization plugin for Vue.js. From 9.0.0-beta.5 until 11.4.14 and 12.0.0-alpha.5, enabling escapeParameter, called escapeParameterHtml in the Legacy API, does not escape named interpolation values when the same translation call supplies both list and named values because escapeParams() processes only the list branch. Applications that render translations as HTML and pass untrusted named values with a list can insert attacker-controlled markup, including phishing links, forms, and layout changes, and can permit script execution when combined with the srcdoc sanitizer bypass or on releases without the sanitizer. This issue is fixed in versions 11.4.14 and 12.0.0-alpha.5.
From the CVE record · GitHub_M
When escapeParameter (escapeParameterHtml in the Legacy API) is enabled, Vue I18n fails to escape named values if the same translation call also supplies list values. If an application renders the translation as HTML and passes an untrusted named value, an attacker can insert markup; script execution is possible with the srcdoc sanitizer bypass or on releases without the sanitizer. Network access, authentication requirements, and user interaction are not specified.
Teams using affected versions of the npm packages vue-i18n, @intlify/core, @intlify/core-base, petite-vue-i18n, or @intlify/vue-i18n-core should check their dependencies.