crypto-tls on Go TLS Handshake resource consumption

Summaryinfo

A vulnerability has been found in crypto-tls on Go and classified as problematic. This issue affects some unknown processing of the component TLS Handshake Handler. Performing a manipulation results in resource consumption. This vulnerability was named CVE-2022-41724. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in crypto-tls on Go (the affected version unknown). It has been classified as problematic. This affects an unknown part of the component TLS Handshake Handler. The manipulation with an unknown input leads to a resource consumption vulnerability. CWE is classifying the issue as CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. This is going to have an impact on availability. The summary by CVE is:

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

The weakness was presented 02/28/2023. The advisory is shared at go.dev. This vulnerability is uniquely identified as CVE-2022-41724 since 09/28/2022. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.

The vulnerability scanner Nessus provides a plugin with the ID 211363 (Ubuntu 22.04 LTS : Go vulnerabilities (USN-7111-1)), which helps to determine the existence of the flaw in a target environment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at Tenable (211363) and CERT Bund (WID-SEC-2023-1141). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

• Amazon Linux 2
• Red Hat Enterprise Linux
• Gentoo Linux
• Red Hat OpenShift
• RESF Rocky Linux

Productinfo

Name

• crypto-tls

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion