CVE-2017-3204

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 3.2%, top 13% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 3%CVSS: 8.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
42(Track)
EG Risk 42/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation3% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
3%
EPSS %ILE
87%
KEV
Not listed

Published

April 4, 2017

Last Modified

June 17, 2026

Advisory Details (5)

Auto-updated Sep 16, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

ssh package - golang.org/x/crypto/ssh - Go Packages

https://godoc.org/golang.org/x/crypto/ssh
generic

x/crypto/ssh: make ClientConfig HostKeyCallback non-permissive by default · Issue #19767 · golang/go · GitHub

https://github.com/golang/go/issues/19767
github_commit

commit e4e2799dd7aa (golang/crypto)

Fix landed in golang/crypto commit e4e2799dd7aa — awaiting tagged release

https://github.com/golang/crypto/commit/e4e2799dd7aab89f583e1d898300d96367750991
generic

Golang SSH Security : The Grumpy Troll

https://bridge.grumpy-troll.org/2017/04/golang-ssh-security/
generic

CVE-2017-3204 - PSIRT.COM

http://www.securityfocus.com/bid/97481

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
golang-go.crypto—1:0.0~git20170407.0.55a552f+REALLY.0.0~git20161012.0.5f31782-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
golang-go.crypto—1:0.0~git20170407.0.55a552f+REALLY.0.0~git20161012.0.5f31782-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
golang-go.crypto—1:0.0~git20170407.0.55a552f+REALLY.0.0~git20161012.0.5f31782-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
golang-go.crypto—1:0.0~git20170407.0.55a552f+REALLY.0.0~git20161012.0.5f31782-1—
Go(1)
PackageVulnerable rangeFixed inDependents
golang.org/x/crypto—0.0.0-20170330155735-e4e2799dd7aa—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 139 total refreshes for this CVE.

  1. 2026-09-18 19:22 UTCEPSS rescore
  2. 2026-09-18 13:06 UTCOSV refresh
  3. 2026-09-17 19:22 UTCEPSS rescore
  4. 2026-09-15 03:05 UTCEPSS rescore
  5. 2026-09-15 03:05 UTCEPSS rescore
  6. 2026-09-13 16:42 UTCEPSS rescore
  7. 2026-09-12 14:55 UTCEPSS rescore
  8. 2026-09-11 09:31 UTCEPSS rescore
  9. 2026-09-07 15:56 UTCEPSS rescore
  10. 2026-09-06 13:43 UTCEPSS rescore
  11. 2026-09-05 15:23 UTCEPSS rescore
  12. 2026-09-04 13:56 UTCEPSS rescore
  13. 2026-09-02 14:07 UTCEPSS rescore
  14. 2026-09-02 14:07 UTCEPSS rescore
  15. 2026-09-01 03:31 UTCEPSS rescore
  16. 2026-08-30 19:13 UTCEPSS rescore
  17. 2026-08-30 14:21 UTCOSV refresh
  18. 2026-08-27 14:21 UTCEPSS rescore
  19. 2026-08-26 14:41 UTCEPSS rescore
  20. 2026-08-25 13:44 UTCEPSS rescore
  21. 2026-08-21 23:44 UTCEPSS rescore
  22. 2026-08-20 22:51 UTCEPSS rescore
  23. 2026-08-19 16:59 UTCEPSS rescore
  24. 2026-08-18 13:43 UTCEPSS rescore
  25. 2026-08-17 13:42 UTCEPSS rescore
Show 75 more
  1. 2026-08-16 14:51 UTCEPSS rescore
  2. 2026-08-16 02:10 UTCEPSS rescore
  3. 2026-08-15 01:26 UTCEPSS rescore
  4. 2026-08-14 03:48 UTCOSV refresh
  5. 2026-08-12 13:46 UTCEPSS rescore
  6. 2026-08-09 13:42 UTCEPSS rescore
  7. 2026-08-07 16:22 UTCEPSS rescore
  8. 2026-08-06 13:42 UTCEPSS rescore
  9. 2026-08-05 19:12 UTCEPSS rescore
  10. 2026-08-04 15:05 UTCEPSS rescore
  11. 2026-08-02 02:23 UTCEPSS rescore
  12. 2026-08-01 04:11 UTCEPSS rescore
  13. 2026-07-30 16:24 UTCEPSS rescore
  14. 2026-07-30 01:26 UTCEPSS rescore
  15. 2026-07-29 08:33 UTCOSV refresh
  16. 2026-07-28 15:32 UTCEPSS rescore
  17. 2026-07-26 14:51 UTCEPSS rescore
  18. 2026-07-23 14:15 UTCEPSS rescore
  19. 2026-07-23 01:29 UTCEG score recompute
  20. 2026-07-22 22:08 UTCEG score recompute
  21. 2026-07-22 14:04 UTCEPSS rescore
  22. 2026-07-22 14:04 UTCEPSS rescore
  23. 2026-07-21 15:21 UTCEPSS rescore
  24. 2026-07-21 15:21 UTCEPSS rescore
  25. 2026-07-20 17:04 UTCEPSS rescore
  26. 2026-07-19 14:28 UTCEPSS rescore
  27. 2026-07-19 14:28 UTCEPSS rescore
  28. 2026-07-19 02:26 UTCEPSS rescore
  29. 2026-07-19 02:26 UTCEPSS rescore
  30. 2026-07-18 10:00 UTCEPSS rescore
  31. 2026-07-16 16:59 UTCEPSS rescore
  32. 2026-07-16 16:59 UTCEPSS rescore
  33. 2026-07-15 16:54 UTCEPSS rescore
  34. 2026-07-15 01:56 UTCEPSS rescore
  35. 2026-07-15 01:56 UTCEPSS rescore
  36. 2026-07-13 22:26 UTCEPSS rescore
  37. 2026-07-12 05:43 UTCEPSS rescore
  38. 2026-07-12 01:11 UTCOSV refresh
  39. 2026-07-11 08:24 UTCEPSS rescore
  40. 2026-07-09 19:06 UTCEPSS rescore
  41. 2026-07-08 15:10 UTCEPSS rescore
  42. 2026-07-07 13:42 UTCEPSS rescore
  43. 2026-07-06 16:24 UTCEPSS rescore
  44. 2026-07-06 16:24 UTCEPSS rescore
  45. 2026-07-06 02:20 UTCEPSS rescore
  46. 2026-07-06 02:20 UTCEPSS rescore
  47. 2026-07-05 02:27 UTCEPSS rescore
  48. 2026-07-04 06:28 UTCEPSS rescore
  49. 2026-07-02 16:54 UTCEPSS rescore
  50. 2026-07-01 15:02 UTCEPSS rescore
  51. 2026-06-30 23:19 UTCEPSS rescore
  52. 2026-06-30 23:19 UTCEPSS rescore
  53. 2026-06-28 04:53 UTCEPSS rescore
  54. 2026-06-27 03:06 UTCEPSS rescore
  55. 2026-06-27 03:05 UTCEPSS rescore
  56. 2026-06-25 13:47 UTCEPSS rescore
  57. 2026-06-24 14:02 UTCEPSS rescore
  58. 2026-06-24 14:02 UTCEPSS rescore
  59. 2026-06-23 07:30 UTCOSV refresh
  60. 2026-06-22 14:23 UTCEPSS rescore
  61. 2026-06-22 14:23 UTCEPSS rescore
  62. 2026-06-21 01:57 UTCEPSS rescore
  63. 2026-06-21 01:57 UTCEPSS rescore
  64. 2026-06-19 19:23 UTCEPSS rescore
  65. 2026-06-19 19:23 UTCEPSS rescore
  66. 2026-06-18 17:50 UTCEPSS rescore
  67. 2026-06-17 17:50 UTCEPSS rescore
  68. 2026-06-16 17:50 UTCEPSS rescore
  69. 2026-06-16 17:50 UTCEPSS rescore
  70. 2026-06-15 17:45 UTCEPSS rescore
  71. 2026-06-14 23:14 UTCEPSS rescore
  72. 2026-06-13 22:57 UTCEPSS rescore
  73. 2026-06-12 23:09 UTCEPSS rescore
  74. 2026-06-10 22:15 UTCEPSS rescore
  75. 2026-06-10 13:19 UTCEPSS rescore

Frequently asked(5)

What is CVE-2017-3204?
CVE-2017-3204 is a high vulnerability published on April 4, 2017. 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.
When was CVE-2017-3204 disclosed?
CVE-2017-3204 was first published in the National Vulnerability Database on April 4, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-3204 actively exploited?
CVE-2017-3204 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3% probability of exploitation in the next 30 days, which ranks it in the top 12.6% of all scored CVEs.
What is the CVSS score of CVE-2017-3204?
CVE-2017-3204 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2017-3204?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-3204, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-3204

Explore →

Is Your Infrastructure Affected by CVE-2017-3204?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs