CVE-2022-41724: Panic on large handshake records in crypto/tls
Golang Go is vulnerable to a denial of service, caused by a flaw when processing large TLS handshake records. By sending specially-crafted TLS handshake records, a remote authenticated attacker could exploit this vulnerability to cause a denial of service condition.
Other sources
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).
— Debian
Panic on large handshake records in crypto/tls
— Microsoft
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2022-41724?
The severity of CVE-2022-41724 is high, with a severity value of 7.5.
How does CVE-2022-41724 affect clients?
CVE-2022-41724 affects all TLS 1.3 clients and TLS 1.2 clients which explicitly enable session resumption, causing panics when attempting to construct responses.
How does CVE-2022-41724 affect servers?
CVE-2022-41724 affects servers when large TLS handshake records are sent by clients, causing servers to panic when attempting to construct responses.
Which versions of Golang are affected by CVE-2022-41724?
Versions 1.19.6 and 1.20.0 of Golang are affected by CVE-2022-41724.
Is there a remedy available for CVE-2022-41724?
Yes, for Golang versions affected by CVE-2022-41724, upgrading to version 1.19.6 or 1.20.1 will address the vulnerability.