ghsa-89mw-w342-mqrr
Vulnerability from github
Published
2023-02-28 18:30
Modified
2023-03-10 06:30
Severity ?
Details
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": [], "aliases": [ "CVE-2022-41724" ], "database_specific": { "cwe_ids": [ "CWE-400" ], "github_reviewed": false, "github_reviewed_at": null, "nvd_published_at": "2023-02-28T18:15:00Z", "severity": "HIGH" }, "details": "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 \u003e= RequestClientCert).", "id": "GHSA-89mw-w342-mqrr", "modified": "2023-03-10T06:30:21Z", "published": "2023-02-28T18:30:17Z", "references": [ { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-41724" }, { "type": "WEB", "url": "https://go.dev/cl/468125" }, { "type": "WEB", "url": "https://go.dev/issue/58001" }, { "type": "WEB", "url": "https://groups.google.com/g/golang-announce/c/V0aBFqaFs_E" }, { "type": "WEB", "url": "https://pkg.go.dev/vuln/GO-2023-1570" }, { "type": "WEB", "url": "https://security.gentoo.org/glsa/202311-09" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "type": "CVSS_V3" } ] }
Loading...
Loading...
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.