Name | CVE-2017-3204 |
Description | 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. |
Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
Debian Bugs | 859655 |
Vulnerable and fixed packages
The table below lists information on source packages.
Source Package | Release | Version | Status |
---|
golang-go.crypto (PTS) | bullseye | 1:0.0~git20201221.eec23a3-1 | fixed |
| bookworm | 1:0.4.0-1 | fixed |
| sid, trixie | 1:0.25.0-1 | fixed |
The information below is based on the following data on fixed versions.
Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
---|
golang-go.crypto | source | (unstable) | 1:0.0~git20170407.0.55a552f+REALLY.0.0~git20161012.0.5f31782-1 | | | 859655 |
Notes
[jessie] - golang-go.crypto <ignored> (In jessie no rdeps using SSH, that version doesn't even support host key validation)
https://github.com/golang/crypto/commit/e4e2799dd7aab89f583e1d898300d96367750991
https://github.com/golang/go/issues/19767