CRLF Injectioni18next-http-backend is an i18next-http-backend is a backend layer for i18next using in Node.js, in the browser and for Deno.
Affected versions of this package are vulnerable to CRLF Injection via the isSafeLangUrlSegment validation function in lib/utils.js, which failed to reject the characters &, =, and ; in lng and ns template values. When a query-shaped load path such as /locales/resources.json?lng={{lng}}&ns={{ns}} is used, an attacker who controls the language or namespace value can inject additional query parameters into the outbound translation API request, overriding or appending parameters such as ns=private&admin=true. A prior fix (3.0.5) only rejected ?, leaving & and = unblocked.
How to fix CRLF Injection? Upgrade i18next-http-backend to version 4.0.4 or higher.
| |
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')i18next-http-backend is an i18next-http-backend is a backend layer for i18next using in Node.js, in the browser and for Deno.
Affected versions of this package are vulnerable to Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') via the interpolateUrl function in lib/utils.js, where a namespace value containing a leading / (permitted for nested namespaces) can combine with the template's own leading / to produce a protocol-relative URL of the form //evil.example/en.json. Browsers treat such URLs as cross-origin requests, allowing an attacker who controls the namespace parameter to redirect translation resource fetches to an arbitrary host and potentially influence application content.
How to fix Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')? Upgrade i18next-http-backend to version 4.0.3 or higher.
| |
Server-side Request Forgery (SSRF)i18next-http-backend is an i18next-http-backend is a backend layer for i18next using in Node.js, in the browser and for Deno.
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via insufficient validation in isSafeUrlSegment functions in lib/utils.js, where user-controlled lng or ns values are interpolated into loadPath/addPath URL templates without rejecting scheme-bearing strings. When a template begins directly with a placeholder (e.g. {{lng}}/{{ns}}.json with no leading origin or path), an attacker can supply a lng value such as http:127.0.0.1:8080 to cause the HTTP backend to issue a request to an arbitrary absolute URL, or an ns value of //evil.example/x to produce a protocol-relative URL in browsers, redirecting requests outside the intended origin.
Note: This is only exploitable when the loadPath or addPath template begins directly with a placeholder, with no leading origin or path segment. The default /locales/{{lng}}/{{ns}}.json template and any template with a leading path or origin are not affected.
How to fix Server-side Request Forgery (SSRF)? Upgrade i18next-http-backend to version 4.0.2 or higher.
| |
Directory Traversali18next-http-backend is an i18next-http-backend is a backend layer for i18next using in Node.js, in the browser and for Deno.
Affected versions of this package are vulnerable to Directory Traversal or other URL manipulation, via unsanitized interpolation of lng and ns values in the loadPath and addPath URL templates in i18nextHttpBackend.js. An attacker can manipulate URL paths to access unintended resources, inject query strings, truncate fragments, or bypass path restrictions.
This allows reads of arbitrary files on the filesystem, if they are readable by loadPath using a scheme such as file://.
How to fix Directory Traversal? Upgrade i18next-http-backend to version 3.0.5 or higher.
| |