QUIC's Connection ID Mechanism vulnerable to Memory Exhaustion Attack
cve-program · CVE-2024-22189
Publishedquic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of `NEW_CONNECTION_ID` frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a `RETIRE_CONNECTION_ID` frame. The attacker can prevent the receiver from sending out (the vast majority of) these `RETIRE_CONNECTION_ID` frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contains a patch for the issue. No known workarounds are available.
Read the publisher's advisoryeuvd · EUVD-2024-1180
Publishedquic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of `NEW_CONNECTION_ID` frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a `RETIRE_CONNECTION_ID` frame. The attacker can prevent the receiver from sending out (the vast majority of) these `RETIRE_CONNECTION_ID` frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contains a patch for the issue. No known workarounds are available.
Read the publisher's advisorynvd · CVE-2024-22189
Publishedquic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of `NEW_CONNECTION_ID` frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a `RETIRE_CONNECTION_ID` frame. The attacker can prevent the receiver from sending out (the vast majority of) these `RETIRE_CONNECTION_ID` frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contains a patch for the issue. No known workarounds are available.
Read the publisher's advisoryosv · GHSA-c33x-xqrf-c478
PublishedAn attacker can cause its peer to run out of memory by sending a large number of NEW_CONNECTION_ID frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a RETIRE_CONNECTION_ID frame. The attacker can prevent the receiver from sending out (the vast majority of) these RETIRE_CONNECTION_ID frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate. I published a more detailed description of the attack and its mitigation in this blog post: https://seemann.io/posts/2024-03-19-exploiting-quics-connection-id-management/. I also presented this attack in the IETF QUIC working group session at IETF 119: https://youtu.be/JqXtYcZAtIA?si=nJ31QKLBSTRXY35U&t=3683 There's no way to mitigate this attack, please update quic-go to a version that contains the fix.
Read the publisher's advisoryosv · GO-2024-2682
PublishedAn attacker can cause its peer to run out of memory by sending a large number of NEW_CONNECTION_ID frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a RETIRE_CONNECTION_ID frame. The attacker can prevent the receiver from sending out (the vast majority of) these RETIRE_CONNECTION_ID frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate.
Read the publisher's advisoryAffected versions, risk and source history
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
cve-program · CVE-2024-22189
PublishedQUIC's Connection ID Mechanism vulnerable to Memory Exhaustion Attack
quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of `NEW_CONNECTION_ID` frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a `RETIRE_CONNECTION_ID` frame. The attacker can prevent the receiver from sending out (the vast majority of) these `RETIRE_CONNECTION_ID` frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contains a patch for the issue. No known workarounds are available.
- Source published
- 4 Apr 2024 14:25:43 UTC
- Source modified
- 23 Aug 2024 19:29:41 UTC
- Saved here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
euvd · EUVD-2024-1180
Publishedquic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of `NEW_CONNECTION_ID` frames that retire old connection IDs. The receiver is suppo…
quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of `NEW_CONNECTION_ID` frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a `RETIRE_CONNECTION_ID` frame. The attacker can prevent the receiver from sending out (the vast majority of) these `RETIRE_CONNECTION_ID` frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contains a patch for the issue. No known workarounds are available.
Additional publisher context
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Apr 4, 2024, 2:25:43 PM
dateUpdated: Aug 23, 2024, 7:29:41 PM
16 related source bulletins · separate from aliases
openSUSE-RU-2026:21160-1: Recommended update for dnscrypt-proxy
CVE-2023-49295 · CVE-2024-22189 · CVE-2026-33186 · CVE-2026-33814
RHSA-2024:5094: Red Hat Security Advisory: Red Hat OpenShift Service Mesh Containers for 2.6.0 security update
CVE-2018-12608 · CVE-2024-22189 · CVE-2024-24789 · CVE-2024-28176
msrc_CVE-2024-22189: QUIC's Connection ID Mechanism vulnerable to Memory Exhaustion Attack
CVE-2024-22189
RHSA-2025:15847: Red Hat Security Advisory: Red Hat OpenShift Dev Spaces 3.23.0 Release.
CVE-2024-10005 · CVE-2024-10006 · CVE-2024-22189 · CVE-2024-24789 · CVE-2024-28869 · CVE-2024-39321 · CVE-2024-45338 · CVE-2025-9287 · CVE-2025-9288 · CVE-2025-48385 · CVE-2025-48387 · CVE-2025-52999
RHSA-2024:4144: Red Hat Security Advisory: VolSync 0.9.2 for RHEL 9
CVE-2024-22189
RHSA-2024:0041: Red Hat Security Advisory: OpenShift Container Platform 4.16.0 bug fix and security update
CVE-2019-25210 · CVE-2023-45142 · CVE-2023-45289 · CVE-2023-47108 · CVE-2023-48795 · CVE-2023-49569 · CVE-2024-0874 · CVE-2024-22189 · CVE-2024-24783 · CVE-2024-24784 · CVE-2024-24785 · CVE-2024-24786 · CVE-2024-28110 · CVE-2024-28176 · CVE-2024-28180 · CVE-2024-28849 · CVE-2024-29180
openSUSE-SU-2024:13847-1: syncthing-1.27.6-1.1 on GA media
CVE-2024-22189
openSUSE-SU-2024:14014-1: caddy-2.8.4-1.1 on GA media
CVE-2024-22189
openSUSE-SU-2024:13865-1: golang-github-v2fly-v2ray-core-5.15.1-1.1 on GA media
CVE-2024-22189
RHSA-2024:8534: Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.5 Product Release Update
CVE-2024-10033 · CVE-2024-22189 · CVE-2024-41989 · CVE-2024-45230
openSUSE-SU-2024:13845-1: kubo-0.27.0-2.1 on GA media
CVE-2024-22189
openSUSE-SU-2024:0220-1: Security update for caddy
CVE-2023-45142 · CVE-2024-22189
openSUSE-SU-2024:0211-1: Security update for caddy
CVE-2023-45142 · CVE-2024-22189
openSUSE-SU-2024:0319-1: Security update for coredns
CVE-2022-27191 · CVE-2022-28948 · CVE-2023-28452 · CVE-2023-30464 · CVE-2024-0874 · CVE-2024-22189
openSUSE-SU-2024:13849-1: coredns-1.11.1-5.1 on GA media
CVE-2024-22189
WID-SEC-W-2024-1474: Red Hat OpenShift Container Platform: Mehrere Schwachstellen
CVE-2019-25210 · CVE-2023-29483 · CVE-2023-45142 · CVE-2023-45289 · CVE-2023-45290 · CVE-2023-47108 · CVE-2023-48795 · CVE-2023-52425 · CVE-2024-0874 · CVE-2024-1394 · CVE-2024-22189 · CVE-2024-2398 · CVE-2024-24783 · CVE-2024-24784 · CVE-2024-24785 · CVE-2024-24786 · CVE-2024-28110 · CVE-2024-28176 · CVE-2024-28180 · CVE-2024-28757 · CVE-2024-28849 · CVE-2024-29180 · CVE-2024-3177 · CVE-2024-3727
- Source published
- Apr 4, 2024, 2:25:43 PM (timezone not stated)
- Source modified
- Aug 23, 2024, 7:29:41 PM (timezone not stated)
- Saved here
- 15 Nov 2026 01:48:42 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 3.1 · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd · CVE-2024-22189
Publishedquic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of `NEW_CONNECTION_ID` frames that retire old connection IDs. The receiver is suppo…
quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of `NEW_CONNECTION_ID` frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a `RETIRE_CONNECTION_ID` frame. The attacker can prevent the receiver from sending out (the vast majority of) these `RETIRE_CONNECTION_ID` frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contains a patch for the issue. No known workarounds are available.
Additional publisher context
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Deferred
Weakness classifications: CWE-770
Original publisher date fields
published: 2024-04-04T15:15:37.990
lastModified: 2026-06-17T07:10:54.083
- Source published
- 4 Apr 2024 15:15:37 UTC
- Source modified
- 17 Jun 2026 07:10:54 UTC
- Saved here
- 24 Oct 2026 23:17:22 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · [email protected] · Secondary · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
osv · GHSA-c33x-xqrf-c478
PublishedQUIC's Connection ID Mechanism vulnerable to Memory Exhaustion Attack
An attacker can cause its peer to run out of memory by sending a large number of NEW_CONNECTION_ID frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a RETIRE_CONNECTION_ID frame. The attacker can prevent the receiver from sending out (the vast majority of) these RETIRE_CONNECTION_ID frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate. I published a more detailed description of the attack and its mitigation in this blog post: https://seemann.io/posts/2024-03-19-exploiting-quics-connection-id-management/. I also presented this attack in the IETF QUIC working group session at IETF 119: https://youtu.be/JqXtYcZAtIA?si=nJ31QKLBSTRXY35U&t=3683 There's no way to mitigate this attack, please update quic-go to a version that contains the fix.
- Source published
- 2 Apr 2024 14:16:05 UTC
- Source modified
- 10 Sep 2026 03:50:11 UTC
- Saved here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Publisher rating · HIGH
osv · GO-2024-2682
PublishedDenial of service via connection starvation in github.com/quic-go/quic-go
An attacker can cause its peer to run out of memory by sending a large number of NEW_CONNECTION_ID frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a RETIRE_CONNECTION_ID frame. The attacker can prevent the receiver from sending out (the vast majority of) these RETIRE_CONNECTION_ID frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate.
- Source published
- 5 Apr 2024 16:53:41 UTC
- Source modified
- 4 Feb 2026 02:49:59 UTC
- Saved here
- 24 Oct 2026 13:19:41 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.