NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

CVE-2017-3204 — x/crypto

HIGHFix: golang/crypto@e4e2799

CVE-2017-3204 is a high-severity (CVSS 8.1) CWE-310 vulnerability in golang.org/x/crypto. A fix is available for golang.org/x/crypto — see the affected versions and patch details below.

golang.org/x/crypto/ssh Man-in-the-Middle attack

Also known asGHSA-xhjq-w7xm-p8qjGO-2020-0013
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
3.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs88th percentile — riskier than 88% of all scored CVEsHighest risk
0.00%1.32%2.64%3.97%0.5%3.2%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐹golang.org/x/crypto

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

The Go SSH library (golang.org/x/crypto/ssh) by default does not verify host keys, facilitating man-in-the-middle attacks if ClientConfig.HostKeyCallback is not set. Default behavior changed in commit e4e2799 to require explicitly registering a hostkey verification mechanism.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogolang.org/x/cryptoall versions0.0.0-20170330155735-e4e2799dd7aago get golang.org/x/crypto@v0.0.0-20170330155735-e4e2799dd7aa

Affected Products

1 product · 1 configurations
Application
cryptogolang
≤ 2017-03-17
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for golang.org/x/crypto, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update golang.org/x/crypto to 0.0.0-20170330155735-e4e2799dd7aa or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-3204 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

The Go SSH library (golang.org/x/crypto/ssh) by default does not verify host keys, facilitating man-in-the-middle attacks if ClientConfig.HostKeyCallback is not set. Default behavior changed in commit e4e2799 to require explicitly registering a hostkey verification mechanism.
O3 Security · Impact-Aware SCA

Is CVE-2017-3204 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2017-3204: x/crypto — Fix Available