CVE-2023-29409: fallo en Go standard library crypto/tls
Large RSA keys can cause high CPU usage in crypto/tls
Publicada el · Actualizada el
Aviso por correo cuando entre en el KEV, tenga PoC pública o suba de nota.
3Vexday Risk Score
Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.
ssvc Trackepss 1.6%
Extremely large RSA keys in certificate chains can cause a client/server to expend significant CPU time verifying signatures. With fix, the size of RSA keys transmitted during handshakes is restricted to <= 8192 bits. Based on a survey of publicly trusted RSA keys, there are currently only three certificates in circulation with keys larger than this, and all three appear to be test certificates that are not actively deployed. It is possible there are larger keys in use in private PKIs, but we target the web PKI, so causing breakage here in the interests of increasing the default safety of users of crypto/tls seems reasonable.
Productos afectados
Go standard library · crypto/tlsCVEs relacionadas — Go standard library crypto/tls
En el mismo producto, de las más peligrosas a las menos.
CVE-2023-39322—Memory exhaustion in QUIC connection handling in crypto/tlsEPSS 1.3%CVE-2023-39321—Panic when processing post-handshake message on QUIC connections in crypto/tlsEPSS 1.3%CVE-2023-45287—Before Go 1.20, the RSA based key exchange methods in crypto/tls may exhibit a timing side channelEPSS 1.3%CVE-2022-30629LOWSession tickets lack random ticket_age_add in crypto/tlsEPSS 1.2%CVE-2022-41724—Panic on large handshake records in crypto/tlsEPSS 1.1%CVE-2025-68121CRITICALUnexpected session resumption in crypto/tlsEPSS 0.9%