9.1

CVE-2024-45337: Misuse of connection.serverAuthenticate may cause authorization bypass in golang.org/x/crypto

Deferred
AliasesSUSE-SU-2025:1142-1SUSE-SU-2025:1143-1openSUSE-SU-2025:0025-1
Published 11-12-2024Last modified 18-02-2025

Vulnerability summary

CVE-2024-45337 is a critical (CVSS 9.1) vulnerability in golang.org/x/crypto golang.org/x/crypto/ssh. EPSS estimates a 3.18% chance of exploitation in the next 30 days, higher than 88% of scored vulnerabilities.

Priority
Prioritisesevere

Severe, CVSS 9.1 (CVE.org); no exploitation reported by the 5 checked sources; EPSS 3% (FIRST, 03-11-2026)

Source freshness unavailable

How is this decided?
CVSS score
9.1/10
010
Critical · v3.1 (CVE.org)
EPSS score
3.18%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 35 · Related 505
MGASA-2026-0147OPENSUSE-SU-2024:14599-1OPENSUSE-SU-2025:0056-1OPENSUSE-SU-2025:0094-1OPENSUSE-SU-2025:14613-1OPENSUSE-SU-2025:14641-1

Showing 100 of 506.

Timeline

  1. 11-12-2024
    PublishedVulnerability first disclosed.
  2. 18-02-2025
    Last modifiedVulnerability information updated.

Description

Applications and libraries which misuse connection.serverAuthenticate (via callback field ServerConfig.PublicKeyCallback) may be susceptible to an authorization bypass. The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions. For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key. Since this API is widely misused, as a partial mitigation golang.org/x/cry...@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth. Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

CVSS metrics

8 scores · 8 sources · 1 version

EPSS trend

Probability

3.18%

Chance of exploitation in the next 30 days

Percentile

88%

Versus all other CVEs

30-day change

No change 0.00 pp

From 3.18% on 04-10-2026

04-10-202603-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

No weakness data has been published for this record.

Affected systems

Version check

Known conditions: network-reachable, no authentication, no user interaction (CVSS vector). Other conditions: not stated in public data.

Chainguard199 products
  • aactl< 0.4.12-r20
  • actions-runner-controller< 0.9.3-r4
  • actions-runner-controller-compat< 0.9.3-r4
  • actions-runner-controller-fips< 0.9.3-r4
  • actions-runner-controller-fips-compat< 0.9.3-r4
Alpine1 product
  • rclone< 1.69.0-r0

2 vendors · 200 products · Showing 200 of 2041

References

38 links
Show all 38 references