Locize gettext-converter
gettext-converter: Prototype pollution in js2i18next() via crafted translation keys
gettext-converter provides gettext resource conversion utilities for JavaScript. Prior to 1.3.3, js2i18next() in lib/js2i18next.js splits nested translation keys using options.keyseparator, whose default value consists of two number signs, and uses each segment as a dynamic object key without rejecting __proto__, constructor, or prototype. When an application converts untrusted PO or i18next translation data, a __proto__ segment resolves Object.prototype as the nested write target and Object.assign writes attacker-controlled translated properties onto the process-wide prototype. The resulting prototype pollution can cause denial of service and may enable application-dependent follow-on attacks. This issue is fixed in version 1.3.3.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 1.3.3
Fixed in 1.3.3
Mitigation
Upgrade gettext-converter to 1.3.3 or later.
References
- Vendor advisory github.com/locize/gettext-converter/security/a…
- Patch github.com/locize/gettext-converter/commit/df9…
- Release notes github.com/locize/gettext-converter/releases/t…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.