SshApplication · Golang
CVE-2020-29652
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 · uneditedA nil pointer dereference in the golang.org/x/crypto/ssh component through v0.0.0-20201203163018-be400aefbc4c for Go allows remote attackers to cause a denial of service against SSH servers.
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 · high confidenceA nil pointer dereference vulnerability in the golang.org/x/crypto/ssh component allows remote attackers to cause denial of service against SSH servers. The vulnerability exists in versions up to v0.0.0-20201203163018-be400aefbc4c and can be triggered by sending specially crafted SSH messages.
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
<= 0.0.0-20201203163018-be400aefbc4cCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate golang.org/x/crypto dependency in go.modSearch your codebase for go.mod files and inspect the require directive for golang.org/x/crypto, noting the version or commit hash shownAffected if The version line shows v0.0.0-20201203163018-be400aefbc4c or an earlier commit hash
-
Verify the crypto/ssh package is importedSearch your source code for 'golang.org/x/crypto/ssh' import statements; grep for 'ssh.Listen' or 'ssh.Server' to confirm SSH server usageAffected if The application imports and uses golang.org/x/crypto/ssh as an SSH server
-
Check vendored dependencies if usedIf your project uses vendor/, inspect vendor/modules.txt or the vendor/golang.org/x/crypto directory for the version manifestAffected if Vendored crypto/ssh version matches <= v0.0.0-20201203163018-be400aefbc4c
-
Query installed module version directlyRun 'go list -m golang.org/x/crypto' in your project directory to display the exact version being usedAffected if The reported version is v0.0.0-20201203163018-be400aefbc4c or earlier
Your environment is affected if the application uses golang.org/x/crypto/ssh as an SSH server and the version is at or below v0.0.0-20201203163018-be400aefbc4c.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate golang.org/x/crypto to a version beyond v0.0.0-20201203163018-be400aefbc4c (preferably the latest stable release) using 'go get golang.org/x/crypto@latest' and rebuild/deploy the affected SSH server applications.
Fix this in Ssh
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-29652 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-29652 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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