Repository navigation
chore(deps): update dependency i18next-fs-backend to v2.6.8 - #221
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.6.7→2.6.8Release Notes
i18next/i18next-fs-backend (i18next-fs-backend)
v2.6.8Compare Source
Security release. Coordinated disclosure from @adamyordan. See published advisory GHSA-cchx-rhgv-92hj.
utils.getLastOfPathnow descends only into own properties, closing an unauthenticated denial of service that the 2.6.6 prototype-pollution fix did not cover. 2.6.6 denylists__proto__,constructorandprototype, but the walk it guards still stepped into inherited members: the autovivify test (!object[key]) is true for every inheritedObject.prototypemethod, so a queued missing-key string such ashasOwnProperty.call(split to['hasOwnProperty','call']inwriteFile()) walked intoObject.prototype.hasOwnPropertyand overwrote its.callwith the attacker's fallback value, breaking the own-property check i18next itself runs and returning500for every request in the process until restart. The same held forvalueOf,toString,isPrototypeOfand the other inherited members the denylist never covered, so extending the denylist would not have closed it. The traversal now gates each descent onObject.prototype.hasOwnProperty.call(object, key), coveringsetPath,pushPathandgetPath, and matching the fix i18next core already carries. Reachable in practice viai18next-http-middleware'smissingKeyHandlerwithsaveMissingenabled; see also the matching fix ini18next-http-middleware3.9.9. Credit: @adamyordan (GHSA-cchx-rhgv-92hj).Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.