# CVE-2023-49295: quic-go's path validation mechanism can cause denial of service > An attacker can exhaust memory in quic-go by sending excessive PATH_CHALLENGE frames, causing a denial of service. - **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 10 Jan 2024 - **Updated:** 17 Jun 2025 - **Also known as:** AZL-33285, AZL-34627, DEBIAN-CVE-2023-49295, GHSA-ppxx-5m9h-6vxf, GO-2024-2459, RHSA-2024:0855, UBUNTU-CVE-2023-49295, openSUSE-SU-2024:13570-1, openSUSE-SU-2025:14626-1 ## What is CVE-2023-49295? CVE-2023-49295 is a medium-severity denial of service vulnerability in quic-go, published on 10 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description quic-go is an implementation of the QUIC protocol (RFC 9000, RFC 9001, RFC 9002) in Go. An attacker can cause its peer to run out of memory sending a large number of PATH_CHALLENGE frames. The receiver is supposed to respond to each PATH_CHALLENGE frame with a PATH_RESPONSE frame. The attacker can prevent the receiver from sending out (the vast majority of) these PATH_RESPONSE frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate. This vulnerability has been patched in versions 0.37.7, 0.38.2 and 0.39.4. Weakness: CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2023-49295? 9 open source packages ship an affected version, including github.com/quic-go/quic-go. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/quic-go/quic-go` | Go | All versions | 0.37.7, 0.38.2, 0.39.4, 0.40.1 | | `github.com/quic-go/quic-go` | Go | All versions | 0.37.7 | | `github.com/quic-go/quic-go` | Go | All versions | 0.37.7 | | `github.com/quic-go/quic-go` | Go | From 0.38.0 | 0.38.2 | | `github.com/quic-go/quic-go` | Go | From 0.38.0 | 0.38.2 | | `github.com/quic-go/quic-go` | Go | From 0.39.0 | 0.39.4 | | `github.com/quic-go/quic-go` | Go | From 0.39.0 | 0.39.4 | | `github.com/quic-go/quic-go` | Go | From 0.40.0 | 0.40.1 | | `github.com/quic-go/quic-go` | Go | From 0.40.0 | 0.40.1 | | `receptor` | Red Hat:ansible_automation_platform:2.4::el8 | All versions | 0:1.4.4-1.el8ap | | `receptor` | Red Hat:ansible_automation_platform:2.4::el9 | All versions | 0:1.4.4-1.el9ap | | `receptor` | Red Hat:ansible_automation_platform_developer:2.4::el8 | All versions | 0:1.4.4-1.el8ap | | `receptor` | Red Hat:ansible_automation_platform_developer:2.4::el9 | All versions | 0:1.4.4-1.el9ap | | `receptor` | Red Hat:ansible_automation_platform_inside:2.4::el8 | All versions | 0:1.4.4-1.el8ap | | `receptor` | Red Hat:ansible_automation_platform_inside:2.4::el9 | All versions | 0:1.4.4-1.el9ap | | `kubo` | openSUSE:Tumbleweed | All versions | 0.32.1-1.1 | Products: Quic-Go Project Quic-Go. ## How do I fix CVE-2023-49295? Upgrade github.com/quic-go/quic-go to a fixed version for your release line: 0.37.7, 0.38.2, 0.39.4 or 0.40.1. ## Is CVE-2023-49295 being exploited? There is no known exploitation of CVE-2023-49295 in the wild and no public exploit code. ## Other vulnerabilities in quic-go - [CVE-2023-46239](https://insights.sbomify.com/CVE-2023-46239/): quic-go vulnerable to pointer dereference that can lead to panic (high 7.5) - [CVE-2022-30591](https://insights.sbomify.com/CVE-2022-30591/): Denial of service in n/a (high 7.5) - [CVE-2026-40898](https://insights.sbomify.com/CVE-2026-40898/): quic-go: HTTP/3 QPACK Trailer Expansion Memory Exhaustion (medium 5.3) - [CVE-2025-64702](https://insights.sbomify.com/CVE-2025-64702/): quic-go HTTP/3 QPACK Header Expansion DoS (medium 5.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-49295 and fix it if it is affected. What it is: CVE-2023-49295 is a medium-severity denial of service vulnerability in quic-go, published on 10 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-49295 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/quic-go/quic-go (Go): affected all versions; fixed in 0.37.7, 0.38.2, 0.39.4, 0.40.1 - github.com/quic-go/quic-go (Go): affected all versions; fixed in 0.37.7 - github.com/quic-go/quic-go (Go): affected all versions; fixed in 0.37.7 - github.com/quic-go/quic-go (Go): affected from 0.38.0; fixed in 0.38.2 - github.com/quic-go/quic-go (Go): affected from 0.38.0; fixed in 0.38.2 - github.com/quic-go/quic-go (Go): affected from 0.39.0; fixed in 0.39.4 - github.com/quic-go/quic-go (Go): affected from 0.39.0; fixed in 0.39.4 - github.com/quic-go/quic-go (Go): affected from 0.40.0; fixed in 0.40.1 - github.com/quic-go/quic-go (Go): affected from 0.40.0; fixed in 0.40.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-2023-49295/ (Markdown: https://insights.sbomify.com/CVE-2023-49295/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-49295 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-49295 - OSV: https://osv.dev/vulnerability/CVE-2023-49295 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-49295/ Summaries are generated and may contain mistakes; the official description above is the record.