Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsUpgrade vue-i18n to version 12.0.0-alpha.5, 11.4.14 or higher.
vue-i18n is an Internationalization plugin for Vue.js
Affected versions of this package are vulnerable to Improper Encoding or Escaping of Output via the sanitizeTranslatedHtml function in packages/shared/src/sanitize.ts, which fails to neutralize srcdoc attributes in translation messages. An attacker who controls translation message content can inject a srcdoc attribute on an <iframe> element; the browser entity-decodes the attribute value and parses it as a full HTML document in the same origin as the page, allowing arbitrary script execution. The existing sanitizer neutralized on* event handlers but did not account for the secondary HTML parsing context that srcdoc introduces, leaving that vector unblocked.
import { createI18n } from 'vue-i18n'
const i18n = createI18n({
legacy: false,
locale: 'en',
escapeParameter: true,
messages: {
en: { message: '<iframe srcdoc="<b>x</b>"></iframe>' }
}
})
console.log(i18n.global.t('message'))
// v11.4.13: <iframe srcdoc="<b>x</b>"></iframe>
The browser decodes the value and renders <b>x</b> as a separate document inside the <iframe>, in the same origin as the page. Any markup in that position is parsed the same way.
Note: The PoC uses vue-i18n with legacy: false and escapeParameter: true, demonstrating that the srcdoc attribute value survives sanitization and is decoded by the browser.