fix(sec): upgrade github.com/btcsuite/btcd to 0.23.2 #7990
Closed
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
yyforyongyu
requested changes
Sep 15, 2023
There was a problem hiding this comment.
Thank you for this PR. Curious about how you generated those mod files, can you provide more details? Such as the commands used, go mod tidy, go work sync?
Also it's interesting to see this report on NIST, https://nvd.nist.gov/vuln/detail/CVE-2022-44797
And finally the git commit message format isn't quite right yet.
|
@realize096, remember to re-request review from reviewers when ready |
|
closed due to inactivity |
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.
What happened？
There are 1 security vulnerabilities found in github.com/btcsuite/btcd v0.22.0-beta.0.20220207191057-4dc4ff7963b4
What did I do？
Upgrade github.com/btcsuite/btcd from v0.22.0-beta.0.20220207191057-4dc4ff7963b4 to 0.23.2 for vulnerability fix
What did you expect to happen？
Ideally, no insecure libs should be used.
How can we automate the detection of these types of issues?
By using the GitHub Actions configurations provided by murphysec, we can conduct automatic code security checks in our CI pipeline.
The specification of the pull request
PR Specification from OSCS