i18next-fs-backend@2.1.0

i18next-fs-backend is a backend layer for i18next using in Node.js and for Deno to load translations from the filesystem.

  • latest version

    2.6.6

  • latest non vulnerable version

  • first published

    6 years ago

  • latest version published

    2 months ago

  • licenses detected

  • Direct Vulnerabilities

    Known vulnerabilities in the i18next-fs-backend 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
    • H
    Prototype Pollution

    i18next-fs-backend is an i18next-fs-backend is a backend layer for i18next using in Node.js and for Deno to load translations from the filesystem.

    Affected versions of this package are vulnerable to Prototype Pollution via the getLastOfPath method. An attacker can modify global object properties and potentially cause application crashes, corrupted behavior, configuration changes, or bypass security checks by submitting crafted missing-key strings containing unsafe segments.

    Note:

    This issue affect users that:

    • expose i18next-http-middleware's missingKeyHandler (or another route that forwards untrusted request bodies to i18next.t(..., { ... }) with saveMissing: true) to untrusted users.

    • use default behaviour of splitting missing-key strings on keySeparator (i.e. keySeparator is not false).

    How to fix Prototype Pollution?

    Upgrade i18next-fs-backend to version 2.6.6 or higher.

    <2.6.6
    • H
    External Control of File Name or Path

    i18next-fs-backend is an i18next-fs-backend is a backend layer for i18next using in Node.js and for Deno to load translations from the filesystem.

    Affected versions of this package are vulnerable to External Control of File Name or Path that leads to raw interpolation of lng and ns values in the loadPath and addPath templates. An attacker can read arbitrary files by passing in traversal sequences such as ?lng=../../../../etc/passwd or overwrite files with the create path if saveMissing is enabled,

    How to fix External Control of File Name or Path?

    Upgrade i18next-fs-backend to version 2.6.4 or higher.

    <2.6.4