Homepage

@intlify/vue-i18n-core@11.4.12

@intlify/vue-i18n-core

  • latest version

    11.4.18

  • latest non vulnerable version

    12.0.0-alpha.9

  • first published

    5 years ago

  • latest version published

    6 days ago

  • licenses detected

  • View vue-i18n-core package health on Snyk  (opens in a new tab)
    • Go back to all versions of this package
    Report a new vulnerability Found a mistake?

    Direct Vulnerabilities

    Known vulnerabilities in the @intlify/vue-i18n-core package. This does not include vulnerabilities belonging to this package’s dependencies.

    Fix vulnerabilities automatically

    Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

    Fix for free
    VulnerabilityVulnerable Version
    • M
    Improper Encoding or Escaping of Output

    @intlify/vue-i18n-core is a @intlify/vue-i18n-core

    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.

    How to fix Improper Encoding or Escaping of Output?

    Upgrade @intlify/vue-i18n-core to version 12.0.0-alpha.5, 11.4.14 or higher.

    >=12.0.0-alpha.4 <12.0.0-alpha.5>=11.1.10 <11.4.14
    • L
    Improper Encoding or Escaping of Output

    @intlify/vue-i18n-core is a @intlify/vue-i18n-core

    Affected versions of this package are vulnerable to Improper Encoding or Escaping of Output via the escapeParams function in packages/core-base/src/translate.ts, when a translation call passes both list and named interpolation values simultaneously. The original logic used else if to escape named values, meaning that when a list argument is also present, named values are never passed through escapeHtml. An attacker who controls a named interpolation value can inject unescaped HTML into the rendered output, enabling a cross-site scripting attack.

    Note: This is only exploitable when the escapeParameter option is explicitly set to true.

    How to fix Improper Encoding or Escaping of Output?

    Upgrade @intlify/vue-i18n-core to version 12.0.0-alpha.5, 11.4.14 or higher.

    >=12.0.0-alpha.1 <12.0.0-alpha.5>=9.2.0-alpha.7 <11.4.14
    Go back to all versions of this package