CVE-2017-3204
CVE-2017-3204 Vulnerability Analysis & Exploit Intelligence
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.
Published Updated Sources: cvelistV5, certcc
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
3%
chance of exploitation in 30 days
CVSS base
Unscored
no source published a base score
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
Weakness & attack patterns
- CWE-310
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Search application, proxy, and WAF logs for requests touching /crypto/ssh).
References
5 on the record
- godoc.org/golang.org/x/crypto/ssh
x_refsource_MISC
- github.com/golang/go/issues/19767
x_refsource_CONFIRM
- bridge.grumpy-troll.org/2017/04/golang-ssh-security/
x_refsource_MISC
- github.com/golang/crypto/commit/e4e2799dd7aab89f583e1d898300d96367750991
x_refsource_CONFIRM
- www.securityfocus.com/bid/97481
vdb-entry, x_refsource_BID
Elsewhere on this site
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.