CVE-2022-41724

Panic on large handshake records in crypto/tls

Description

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).

Category

7.5
CVSS
Severity: High
CVSS 3.1 •
EPSS 0.02%
Vendor Advisory go.dev Vendor Advisory google.com Vendor Advisory go.dev
Affected: Go standard library crypto/tls
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2022-41724?
CVE-2022-41724 has been scored as a high severity vulnerability.
How to fix CVE-2022-41724?
To fix CVE-2022-41724, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2022-41724 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2022-41724 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2022-41724?
CVE-2022-41724 affects Go standard library crypto/tls.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.