[Cycode] Fix for vulnerable manifest file dependency - golang.org/x/crypto updated to version 0.52.0 - #99
Open
cycode-security[bot] wants to merge 1 commit into
Conversation
…rypto updated to version 0.52.0
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.
Cycode Vulnerable Dependencies Update
This pull request updates the following manifest file:
go.mod📂 go.mod
1 package will be updated to resolve vulnerabilities:
golang.org/x/cryptoNote
Medium Risk
Touches a security-sensitive dependency used for bcrypt password handling; risk is moderate because behavior should be unchanged but crypto upgrades warrant normal regression checks.
Overview
Bumps the direct
golang.org/x/cryptodependency ingo.modfrom 0.41.0 to 0.52.0 to address reported vulnerabilities (Cycode-driven update). No application source changes are included in this diff.That module is used in this repo for password hashing via
golang.org/x/crypto/bcrypt(e.g.internal/api/crypto/hash.go), so the change is limited to the resolved crypto library version at build time.Reviewed by Cursor Bugbot for commit 4a2eba8. Configure here.