-
Notifications
You must be signed in to change notification settings - Fork 301
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade golang.org/x/crypto to version 0.0.0-20200220183623-bac4c82f6975 or higher. #451
Upgrade golang.org/x/crypto to version 0.0.0-20200220183623-bac4c82f6975 or higher. #451
Comments
Thanks for submitting this issue, @IzhakJakov ! Thanks to your write-up its clear that this has something to do with the version of our gRPC dependency. We'll put this into our planning process. |
Thank you. |
What is the expected completion date for this issue? |
Thanks for following up, we are short staffed right now, so this fell off the radar. I don't think its going to make this upcoming release, but it will definitely make the next one. |
We will try to get this out ASAP in a micro release |
Sounds good. Thank you! |
It seems this comes from the older version of grpc we have in our |
Thanks for taking care of this :) |
Description
golang.org/x/crypto is a SSH client and server
Affected versions of this package are vulnerable to Improper Signature Verification. An attacker can craft an
ssh-ed25519
or[email protected]
public key, such that the library will panic when trying to verify a signature with it. Clients can deliver such a public key and signature to anygolang.org/x/crypto/ssh
server with aPublicKeyCallback
, and servers can deliver them to anygolang.org/x/crypto/ssh
clientReference: https://security.snyk.io/vuln/SNYK-GOLANG-GOLANGORGXCRYPTO-1083910
Steps to Reproduce
Expected Behavior
The text was updated successfully, but these errors were encountered: