dbcve.org
SshApplication · Golang

CVE-2022-27191

HIGH · 7.5 CVSS v3.1 Published 2022-03-18
Fix available
A fix is available. Upgrade to 0.0.0-20220314234659-1baeb1ce4c0b or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The golang.org/x/crypto/ssh package before 0.0.0-20220314234659-1baeb1ce4c0b for Go allows an attacker to crash a server in certain circumstances involving AddHostKey.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The golang.org/x/crypto/ssh package contains a denial-of-service vulnerability where AddHostKey can be triggered in certain circumstances to crash an SSH server. This affects versions prior to 0.0.0-20220314234659-1baeb1ce4c0b.

MitigationUpgrade golang.org/x/crypto/ssh to version 0.0.0-20220314234659-1baeb1ce4c0b or later, then rebuild and redeploy affected services.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SshApplication
Affected:< 0.0.0-20220314234659-1baeb1ce4c0b
FedoraOperating system
Affected:= 34= 35= 36
Advanced Cluster Management For KubernetesApplication
Affected:= 2.0
Extra Packages For Enterprise LinuxApplication
Affected:= 8.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify golang.org/x/crypto/ssh version
    Run 'go list -m golang.org/x/crypto' or inspect go.mod file for the crypto/ssh dependency version
    Affected if Version is earlier than 0.0.0-20220314234659-1baeb1ce4c0b
  2. Verify SSH server is in use
    Search code for usage of golang.org/x/crypto/ssh ServerConfig and call to AddHostKey method
    Affected if Code uses ssh.ServerConfig with AddHostKey function to add host keys
  3. Check Fedora version
    Run 'cat /etc/fedora-release' or 'rpm -q fedora-release'
    Affected if Version is 34, 35, or 36 and uses vulnerable crypto/ssh package
  4. Check Redhat ACM for Kubernetes version
    Run 'oc get csv -A | grep advanced-cluster-management' or check operator version
    Affected if Version is 2.0 and contains vulnerable golang.org/x/crypto/ssh package
  5. Check EPEL 8 package version
    Run 'rpm -q golang-x-crypto' on Enterprise Linux 8 system
    Affected if EPEL 8.0 package is installed containing vulnerable crypto/ssh

Environment is affected if golang.org/x/crypto/ssh version is below 0.0.0-20220314234659-1baeb1ce4c0b AND the SSH server AddHostKey function is used, or if running the specific affected product versions listed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.0.0-20220314234659-1baeb1ce4c0b or later
Fixed in 0.0.0-20220314234659-1baeb1ce4c0b
Interim mitigation

Upgrade golang.org/x/crypto/ssh to version 0.0.0-20220314234659-1baeb1ce4c0b or later, then rebuild and redeploy affected services.

Recommended fix Moderate confidence

golang.org/x/crypto/ssh version 0.0.0-20220314234659-1baeb1ce4c0b or later

  1. For Go projects using golang.org/x/crypto/ssh: Run 'go get golang.org/x/crypto/ssh' to update to the latest version which includes the fix
  2. For Fedora systems (34, 35, 36): Run 'dnf update golang-x-crypto' or 'dnf update --security' to apply available security updates
  3. For Advanced Cluster Management for Kubernetes 2.0: Apply the security patch or upgrade to a version that includes the fixed golang.org/x/crypto/ssh package
  4. For EPEL 8.0: Run 'dnf update' or 'yum update' to apply the latest security fixes
  5. After updating, rebuild and restart any services that use the SSH package to ensure the fix is applied

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ssh Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-27191 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-27191 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data