Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.1

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

CVE-2017-3204GHSA-xhjq-w7xm-p8qj

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (golang.org/x/crypto 0.0.0-20170330155735-e4e2799dd7aa), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go golang.org/x/crypto

    Affected
    < 0.0.0-20170330155735-e4e2799dd7aa
    Fixed in
    0.0.0-20170330155735-e4e2799dd7aa

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.1 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2017-3204: 3.16% estimated exploitation activity in the next 30 days; percentile 87.98 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-xhjq-w7xm-p8qj

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2017-3204

Advisory: golang.org/x/crypto/ssh Man-in-the-Middle attack
IDs: CVE-2017-3204, GHSA-xhjq-w7xm-p8qj
Record: https://patchnext.com/advisories/cve-2017-3204 (revision 1, source checked 26 Oct 2026, 15:03 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: golang.org/x/crypto 0.0.0-20170330155735-e4e2799dd7aa. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go golang.org/x/crypto: affected < 0.0.0-20170330155735-e4e2799dd7aa; fixed in 0.0.0-20170330155735-e4e2799dd7aa

## Suggested inspection (read-only)
- Go golang.org/x/crypto: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on golang.org/x/crypto.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-xhjq-w7xm-p8qj (GitHub-reviewed advisory GHSA-xhjq-w7xm-p8qj lists affected ranges: Go golang.org/x/crypto >=0 <0.0.0-20170330155735-e4e2799dd7aa)

Commands are suggestions: review each one before running it.

Loading voting…