# CVE-2022-41724: Panic on large handshake records in crypto/tls > Attackers can cause a denial of service by sending large TLS handshake records, affecting Go applications with specific TLS configurations. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 28 Feb 2023 - **Updated:** 7 Mar 2025 - **Also known as:** AZL-13731, AZL-13737, AZL-34755, AZL-37400, AZL-37508, AZL-78952, AZL-98751, BIT-golang-2022-41724, DEBIAN-CVE-2022-41724, GHSA-89mw-w342-mqrr, GO-2023-1570, MINI-f8q6-g439-w688, RHSA-2023:3303, UBUNTU-CVE-2022-41724 ## What is CVE-2022-41724? CVE-2022-41724 is a high-severity denial of service vulnerability in Golang Go, published on 28 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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). Weakness: CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2022-41724? 2 open source packages ship an affected version, including golang and stdlib. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `golang` | Bitnami | All versions | 1.19.6, 1.20.1 | | `stdlib` | Go | All versions | 1.19.6, 1.20.1 | | `cri-o` | Red Hat:openshift:4.13::el8 | All versions | 0:1.26.3-6.rhaos4.13.gitb3475fb.el8 | | `cri-o-debuginfo` | Red Hat:openshift:4.13::el8 | All versions | 0:1.26.3-6.rhaos4.13.gitb3475fb.el8 | | `cri-o-debugsource` | Red Hat:openshift:4.13::el8 | All versions | 0:1.26.3-6.rhaos4.13.gitb3475fb.el8 | | `cri-o` | Red Hat:openshift:4.13::el9 | All versions | 0:1.26.3-7.rhaos4.13.gitb3475fb.el9 | | `cri-o-debuginfo` | Red Hat:openshift:4.13::el9 | All versions | 0:1.26.3-7.rhaos4.13.gitb3475fb.el9 | | `cri-o-debugsource` | Red Hat:openshift:4.13::el9 | All versions | 0:1.26.3-7.rhaos4.13.gitb3475fb.el9 | Products: Golang Go. ## How do I fix CVE-2022-41724? Upgrade golang to a fixed version for your release line: 1.19.6 or 1.20.1. ## Is CVE-2022-41724 being exploited? There is no known exploitation of CVE-2022-41724 in the wild and no public exploit code. ## Other vulnerabilities in Golang Go - [CVE-2020-0601](https://insights.sbomify.com/CVE-2020-0601/): Microsoft Windows CryptoAPI Spoofing (high 8.1, exploited in the wild) - [CVE-2026-27143](https://insights.sbomify.com/CVE-2026-27143/): Missing bound checks can lead to memory corruption in safe Go in cmd/compile (critical 9.8) - [CVE-2024-24790](https://insights.sbomify.com/CVE-2024-24790/): Unexpected behavior from Is methods for IPv4-mapped IPv6 addresses in net/netip (critical 9.8) - [CVE-2023-39320](https://insights.sbomify.com/CVE-2023-39320/): Arbitrary code execution via go.mod toolchain directive in cmd/go (critical 9.8) - [CVE-2023-24540](https://insights.sbomify.com/CVE-2023-24540/): Improper handling of JavaScript whitespace in html/template (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-41724 and fix it if it is affected. What it is: CVE-2022-41724 is a high-severity denial of service vulnerability in Golang Go, published on 28 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2022-41724 in the wild and no public exploit code. Affected packages and fixed versions: - golang (Bitnami): affected all versions; fixed in 1.19.6, 1.20.1 - stdlib (Go): affected all versions; fixed in 1.19.6, 1.20.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-41724/ (Markdown: https://insights.sbomify.com/CVE-2022-41724/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-41724 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-41724 - OSV: https://osv.dev/vulnerability/CVE-2022-41724 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-41724/ Summaries are generated and may contain mistakes; the official description above is the record.