llamaCVEVulnerability Intelligence
/
golang.org/x/crypto/ssh

CVE-2024-45337

Misuse of connection.serverAuthenticate may cause authorization bypass in golang.org/x/crypto

Texto original en inglés · Ver en español

Parche disponible
Descargar PNG JSON
CVSS 3.1
9.1
Crítica
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N Fuente: CISA-ADP
ExplotaciónSin evidenciaSSVC: none · no figura en CISA KEV
Exploits públicos51 fuente
Parche2 versionesPrimer parche el mismo día de la divulgación
Exposición709 dDesde la divulgación, 11 dic 2024, 1:55 p. m.
Detección705 dDesde la divulgación hasta su ingreso al índice
Decisión SSVCAtender
Priorizar en el próximo ciclo de cambios
Sin explotación conocida, automatizable e impacto técnico total. Hay versiones corregidas disponibles.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Evaluación SSVC
Modificada
Explotación
Remediación
Parche v0.31.0
Monitoreo
Detectada
11 dic 24
12 dic 24
18 feb 25
17 nov 26
20 nov 26
11 dic 24
7 jun 25
1 dic 25
27 may 26
20 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2024-45337 divulgada · CVSS 9.1 (CISA-ADP)
Remediación Parche v0.31.0 golang.org/x/crypto · 0 d desde divulgación
Divulgación Evaluación SSVC CISA-ADP · explotación ninguna
Divulgación Modificada Última actualización del registro
Monitoreo Detectada Ingresó al índice
Resumen

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.

Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · CISA-ADP
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
PrivilegiosPR:N
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:H
AltoBajoNinguno
DisponibilidadA:N
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida Última
golang.org/x/crypto/ssh · golang.org/x/crypto< 0.31.0
0.31.0
v0.59.0
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
gogolang.org/x/crypto
Corregida v0.31.0 0 d v0.59.0 no afectada
Versiones corregidas0.31.0v0.31.0
Explotación

Arsenal público

Exploit-DB
—
0
Metasploit
—
0
Nuclei
—
0
PoC en GitHub
Backline-playground/gogs · NHAS/CVE-2024-45337-POC · NHAS/VULNERABLE-CVE-2024-45337 · ferralon-demo/gitea-cve-2024-45337 · peace-maker/CVE-2024-45337
5
Ver los 5 repositorios de GitHub
Backline-playground/gogs
NHAS/CVE-2024-45337-POC
NHAS/VULNERABLE-CVE-2024-45337
ferralon-demo/gitea-cve-2024-45337
peace-maker/CVE-2024-45337

Los repositorios públicos incluyen exploits, escáneres, laboratorios y reglas de detección. No ejecute código de terceros sin revisarlo en un entorno aislado.

Referencias
Análisishttp://www.openwall.com/lists/oss-security/2024/12/11/2
Exploithttps://github.com/Backline-playground/gogs
Exploithttps://github.com/NHAS/CVE-2024-45337-POC
Exploithttps://github.com/NHAS/VULNERABLE-CVE-2024-45337
Exploithttps://github.com/ferralon-demo/gitea-cve-2024-45337
Exploithttps://github.com/peace-maker/CVE-2024-45337
Otrahttps://github.com/golang/crypto/commit/b4f1988a35dee11ec3e05d6bf3e90b695fbd8909
Otrahttps://go.dev/cl/635315
Otrahttps://go.dev/issue/70779
Otrahttps://groups.google.com/g/golang-announce/c/-nPEi39gI4Q/m/cGVPJCqdAQAJ
Otrahttps://pkg.go.dev/vuln/GO-2024-3321
Otrahttps://security.netapp.com/advisory/ntap-20250131-0007/

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.