CVE-2017-3204 json
golang.org/x/crypto/ssh Man-in-the-Middle attack
published 2017-04-04 9 y ago modified 2026-06-17 4 mo ago also GHSA-xhjq-w7xm-p8qj , GO-2020-0013 , EUVD-2023-0819
- cvss
- 8.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.2%
- EPSS 3.2% chance of exploitation in 30 days, percentile 88%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go golang.org/x/crypto 0.0.0-20170330155735-e4e2799dd7aa
- golang-go.crypto Debian 14, Debian 13, Debian 12 1:0.0~git20170407.0.55a552f+REALLY.0.0~git20161012.0.5f31782-1
debian advisories DEBIAN-CVE-2017-3204
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2017-3204 updated cvss 4.8
golang-googlecode-go-crypto: Go SSH library does not verify host keys by default
-
Red Hat Enterprise Linux 7 gomtree, kubernetes Red Hat OpenShift Enterprise 3 atomic-openshift, atomic-openshift-pod, atomic-openshift-node, atomic-openshift-tests, atomic-openshift-master, atomic-openshift-clients, +13 more Red Hat Software Collections rh-mongodb32-golang-googlecode-go-crypto-unit-testnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
3.16% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | golang.org/x/crypto | <0.0.0-20170330155735-e4e2799dd7aa |
0.0.0-20170330155735-e4e2799dd7aa |
Affected products
- Go SSH library
Classification
- Weakness
-
- CWE-310 Cryptographic Issues
References
-
github.com
/golang/crypto/commit/e4e2799dd7aab89f583e1d898300d96367750991
web, patch, third-party-advisory
-
go.googlesource.com
/crypto/+/e4e2799dd7aab89f583e1d898300d96367750991
web, patch
-
go.dev
/cl/38701
web, patch
-
godoc.org
/golang.org/x/crypto/ssh
web, vendor-advisory
-
github.com
/golang/go/issues/19767
web, third-party-advisory
-
bridge.grumpy-troll.org
/2017/04/golang-ssh-security/
third-party-advisory, web
-
securityfocus.com
/bid/97481
vdb-entry, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2017-3204
advisory
-
bridge.grumpy-troll.org
/2017/04/golang-ssh-security
web
-
go.dev
/cl/340830
web
-
go.dev
/issue/19767
web, report
-
pkg.go.dev
/vuln/GO-2020-0013
web
-
web.archive.org
/web/20170423080311/https://www.securityfocus.com/bid/97481
web
-
web.nvd.nist.gov
/view/vuln/detail?vulnId=CVE-2017-3204
web
Sources
- CVE List CVE-2017-3204
- GitHub Advisory GHSA-xhjq-w7xm-p8qj
- NVD CVE-2017-3204
- OSV GO-2020-0013
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.