CVE-2017-3204

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: 2017-04-04 Last update: 2026-05-13 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2017-3204 is rated High Risk (65.2/100): CVSS High severity, with medium exploitation likelihood (EPSS 3.16%). EPSS rose +2.62% over the last day, indicating growing attacker interest. High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2017-3204

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.53% 3.16% +2.62%
2 2026-02-08 1.81% 0.53% -1.28%
3 2025-07-22 — 1.81% —

Full EPSS history (10 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-3204

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.1 3.1 HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.2 5.9 [email protected]
6.8 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 6.4 [email protected]

Weakness enumeration for CVE-2017-3204

GitHub Security Advisory for CVE-2017-3204

GHSA-xhjq-w7xm-p8qj · Severity: high · Ecosystem: go — golang.org/x/crypto/ssh Man-in-the-Middle attack

OS Trackers for CVE-2017-3204

vendor priority summary link
debian not yet assigned CVE-2017-3204 not yet assigned priority: Debian including 1 source packages (golang-go.crypto), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2017-3204
redhat medium — https://access.redhat.com/security/cve/CVE-2017-3204
ubuntu low CVE-2017-3204 low priority: Ubuntu including 3 source packages (golang-go.crypto, snapd, ubuntu-snappy), 69 status rows across 23 suites (artful, bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, precise, questing, trusty, upstream, xenial, yakkety, zesty): DNE 26, ignored 23, not-affected 16, needs-triage 2, needed 1, released 1. https://ubuntu.com/security/CVE-2017-3204

Affected software / configurations for CVE-2017-3204

Vendor Product Version Raw CPE
golang crypto <= 2017-03-17 cpe:2.3:a:golang:crypto:*:*:*:*:*:*:*:*

References for CVE-2017-3204

cvelogic Threat Intelligence