Vulnerabilities · 2017 · Golang
CVE-2017-3204
Golang Crypto vulnerability
The Go SSH library (x/crypto/ssh) by default does not verify host keys, facilitating man-in-the-middle attacks. Default behavior changed in commit e4e2799 to require explicitly registering a hostkey verification mechanism.
Affected products
Crypto. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Golang Crypto runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- godoc.org/golang.org/x/crypto/ssh · Vendor Advisory
- github.com/golang/crypto/commit/e4e2799dd7aab89f583e1d898300d96367750991 · Patch
- www.securityfocus.com/bid/97481 · Third Party Advisory
- bridge.grumpy-troll.org/2017/04/golang-ssh-security/ · Third Party Advisory
- github.com/golang/go/issues/19767 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2017-3204
- go.dev/cl/340830
- go.dev/issue/19767
- nvd.nist.gov/vuln/detail/CVE-2017-3204
- cve.org/CVERecord?id=CVE-2017-3204
More vulnerabilities in Golang products
CVE-2026-42506CVE-2026-42502CVE-2026-27136CVE-2026-25681CVE-2026-25680CVE-2025-68121CVE-2025-68119CVE-2025-61732All 172
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.