CVE-2022-41724: vulnerability in Go standard library crypto/tls
Panic on large handshake records in crypto/tls
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
3Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackepss 1.1%
Large handshake records may cause panics in crypto/tls. Both clients and servers may send large TLS handshake records which cause servers and clients, respectively, to panic when attempting to construct responses. This affects all TLS 1.3 clients, TLS 1.2 clients which explicitly enable session resumption (by setting Config.ClientSessionCache to a non-nil value), and TLS 1.3 servers which request client certificates (by setting Config.ClientAuth >= RequestClientCert).
Affected products
Go standard library · crypto/tlsRelated CVEs — Go standard library crypto/tls
In the same product, most dangerous first.
CVE-2023-29409—Large RSA keys can cause high CPU usage in crypto/tlsEPSS 1.6%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-2025-68121CRITICALUnexpected session resumption in crypto/tlsEPSS 0.9%