go.mod: bump x/crypto to v0.31.0 #271
Merged
+21
−21
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
The crypto experimental module that the SDK depends on was detected vulnerable on v0.23.0 to an authentication bypass attack through the ServerConfig for SSH. This is only used for locally proxying SSH communications, typically for use with Ansible to provide an SSH server with which to interact, in order to provision an instance of an OS that uses a communicator other than SSH, therefore the vulnerability does not necessarily impact us. However, in order to resolve the automatic report of that vulnerability, we bump the crypto module's version to 0.31.0, where that problem was addressed.
JenGoldstrich
approved these changes
Dec 17, 2024
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.
The crypto experimental module that the SDK depends on was detected vulnerable on v0.23.0 to an authentication bypass attack through the ServerConfig for SSH.
This is only used for locally proxying SSH communications, typically for use with Ansible to provide an SSH server with which to interact, in order to provision an instance of an OS that uses a communicator other than SSH, therefore the vulnerability does not necessarily impact us. However, in order to resolve the automatic report of that vulnerability, we bump the crypto module's version to 0.31.0, where that problem was addressed.