What is CVE-2024-45337?

Applications using crypto/ssh's ServerConfig.PublicKeyCallback may incorrectly authorize connections when the callback approves a key but authentication fails, due to a logic flaw in the authentication flow.

How do I fix CVE-2024-45337?

Upgrade Go to 1.22.10+ or 1.23.4+. Review your PublicKeyCallback implementation to ensure it rejects unauthorized keys. Add explicit key allowlist validation inside PublicKeyCallback. Rotate SSH host keys and audit SSH access logs for anomalies. Run static analysis (govulncheck) to detect usage of vulnerable patterns. Pin allowed public keys in your callback rather than relying on post-callback checks.

Which versions are affected by CVE-2024-45337?

Affected: Go < 1.22.10, < 1.23.4. Fixed in: Go 1.22.10+, 1.23.4+.

criticalCVSS 9.1/10·Published: 2024-12-11·Go standard library (crypto/ssh)

How to fix CVE-2024-45337 – Step-by-Step Guide

CVE-2024-45337 addresses a critical authentication bypass in Go's `crypto/ssh` library. Named 'Misuse of ServerConfig.PublicKeyCallback', this flaw allows unauthorized access to SSH servers built with affected Go versions, posing a severe security risk.

CVE ID

CVE-2024-45337

Severity

CRITICAL

CVSS Score

9.1/10

Affected

Go standard library (crypto/ssh)

What is Go crypto/ssh – Misuse of ServerConfig.PublicKeyCallback?

The vulnerability stems from a logic flaw in `crypto/ssh`'s `ServerConfig.PublicKeyCallback`. If an application's callback approves a key but authentication fails, the connection may still be incorrectly authorized. This bypasses intended authentication, affecting Go versions prior to 1.22.10 and 1.23.4.

Affected Versions

Go < 1.22.10, < 1.23.4

Fixed In

Go 1.22.10+, 1.23.4+

Official References

Impact and Risks for your Infrastructure

This critical flaw enables unauthorized SSH authentication bypass, allowing attackers to access Go applications using any public key. This can lead to severe data breaches, system compromise, and unauthorized control over affected infrastructure, posing significant security risks.

gosshauth-bypasscritical2024

Step-by-Step Mitigation Guide

To mitigate CVE-2024-45337, upgrade your Go applications to Go 1.22.10+ or 1.23.4+. Verify the fix by ensuring your Go environment is updated and re-deploying affected services. Regularly audit `PublicKeyCallback` implementations for correct authentication logic to prevent similar issues.

1Upgrade Go to 1.22.10+ or 1.23.4+.
2Review your PublicKeyCallback implementation to ensure it rejects unauthorized keys.
3Add explicit key allowlist validation inside PublicKeyCallback.
4Rotate SSH host keys and audit SSH access logs for anomalies.
5Run static analysis (govulncheck) to detect usage of vulnerable patterns.
6Pin allowed public keys in your callback rather than relying on post-callback checks.

Frequently Asked Questions

What is the CVSS score for CVE-2024-45337?▼

CVE-2024-45337 has a CVSS score of 9.1/10 (critical severity). This reflects the most severe potential impact, requiring immediate remediation.

Which versions of Go standard library (crypto/ssh) are affected?▼

Affected: Go < 1.22.10, < 1.23.4. The vulnerability was fixed in: Go 1.22.10+, 1.23.4+.

How long does it take to fix CVE-2024-45337?▼

For most teams: 15–60 minutes to apply the patch, plus 15 minutes of post-patch verification. Complex multi-service environments may require 2–4 hours including staging validation.

Is CVE-2024-45337 being actively exploited?▼

Check the NVD entry and CISA KEV catalog for exploitation status. As a critical-severity vulnerability, treat it as a priority remediation regardless of known exploitation status.

Run Security Check →Browse Runbooks →← All CVE Solutions

This CVE fix guide is based on publicly available security advisories (NVD, vendor bulletins). Always test changes in a staging environment before applying to production. Verify against the official vendor advisory for the most up-to-date guidance.