First published: Tue Apr 04 2017(Updated: )
The Go SSH library (golang.org/x/crypto/ssh) by default does not verify host keys, facilitating man-in-the-middle attacks if ClientConfig.HostKeyCallback is not set. Default behavior changed in commit e4e2799 to require explicitly registering a hostkey verification mechanism.
Credit: cret@cert.org cret@cert.org
Affected Software | Affected Version | How to fix |
---|---|---|
go/golang.org/x/crypto | <0.0.0-20170330155735-e4e2799dd7aa | 0.0.0-20170330155735-e4e2799dd7aa |
golang.org/x/crypto | <=2017-03-17 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-3204 is considered a medium severity vulnerability due to the risk of man-in-the-middle attacks.
To fix CVE-2017-3204, ensure that the ClientConfig.HostKeyCallback is explicitly set to verify host keys.
CVE-2017-3204 affects versions of the Go SSH library prior to the commit e4e2799.
CVE-2017-3204 facilitates man-in-the-middle attacks by not verifying host keys.
Yes, the default behavior of the Go SSH library does not verify host keys, posing a security risk.