Bump semver to ensure signed provenance, CVE fix #123
Merged
Conversation
This file contains 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
Mrtenz
previously approved these changes
Jul 21, 2023
Mrtenz
approved these changes
Jul 25, 2023
|
Just rebased the pull request, it had conflicts in |
GuillaumeRx
approved these changes
Jul 25, 2023
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.
Problem: Many snaps recently audited used vulnerable package during audits/reviews.
Solutions: Bumping semver to ^7.5.4 (latest) in MetaMask/snaps and MetaMask/utils to ensure snap authors (and all other future imports) use version built/signed with provenance (new in >= 7.5.1) and fix CVE-2022-25883 (>= 7.5.2).
I spoke with @FrederikBolding yesterday, related PRs:
semveras requested by Dependabot snaps#1603