How severe is GHSA-3vm4-22fp-5rfm?

GHSA-3vm4-22fp-5rfm has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-3vm4-22fp-5rfm?

GHSA-3vm4-22fp-5rfm affects the following packages: golang.org/x/crypto (Go). Ecosystems affected: Go.

How do I fix GHSA-3vm4-22fp-5rfm?

Update golang.org/x/crypto to 0.0.0-20201216223049-8b5274cf687f or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3vm4-22fp-5rfm is resolved across your whole dependency graph.

How do I detect GHSA-3vm4-22fp-5rfm in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for golang.org/x/crypto. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-3vm4-22fp-5rfm if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-3vm4-22fp-5rfm?

O3 pinpoints whether GHSA-3vm4-22fp-5rfm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-3vm4-22fp-5rfm actively exploited in the wild?

No public exploit code has been indexed for GHSA-3vm4-22fp-5rfm yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-3vm4-22fp-5rfm?

GHSA-3vm4-22fp-5rfm has an EPSS (Exploit Prediction Scoring System) score of 3.2%, placing it in the 87th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-3vm4-22fp-5rfm published, and has it been updated?

GHSA-3vm4-22fp-5rfm was published on May 24, 2022 and was last updated on February 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-3vm4-22fp-5rfm

HIGH

golang.org/x/crypto/ssh NULL Pointer Dereference vulnerability

Also known asCVE-2020-29652GO-2021-0227

Published

May 24, 2022

Updated

Feb 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

3.2%probability of exploitation in next 30 days

Lower Risk87th percentile+3.20%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

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

A 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. An attacker can craft an authentication request message for the gssapi-with-mic method which will cause NewServerConn to panic via a nil pointer dereference if ServerConfig.GSSAPIWithMICConfig is nil.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`golang.org/x/crypto`	all versions	0.0.0-20201216223049-8b5274cf687f

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for golang.org/x/crypto. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update golang.org/x/crypto to 0.0.0-20201216223049-8b5274cf687f or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3vm4-22fp-5rfm is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-3vm4-22fp-5rfm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-3vm4-22fp-5rfm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A 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. An attacker can craft an authentication request message for the `gssapi-with-mic` method which will cause NewServerConn to panic via a nil pointer dereference if ServerConfig.GSSAPIWithMICConfig is nil.

O3 Security · Impact-Aware SCA

Is GHSA-3vm4-22fp-5rfm in your dependencies?

O3 detects GHSA-3vm4-22fp-5rfm across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works