quiche vulnerable to unbounded storage of information related to connection ID retirement
CVE-2024-1410GHSA-xhg9-xwch-vr7x
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (quiche 0.20.1, 0.19.2), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
crates.io quiche
- Affected
- < 0.19.2>= 0.20.0, < 0.20.1
- Fixed in
- 0.20.1, 0.19.2
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-xhg9-xwch-vr7x lists affected ranges: crates.io quiche >=0 =0.20.0 <0.20.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 3.7 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
- EPSS
- CVE-2024-1410: 0.66% estimated exploitation activity in the next 30 days; percentile 51.72 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Impact 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. Endpoints declare the number of active connection IDs they are willing to support using the activeconnectionidlimit transport parameter. The peer can create new IDs using a NEWCONNECTIONID frame but must stay within the active ID limit. This is done by retirement of old IDs, the endpoint sends NEWCONNECTIONID includes a value in the retirepriorto field, which elicits a RETIRECONNECTIONID frame as confirmation. An unauthenticated remote attacker can exploit the vulnerability by sending NEWCONNECTIONID frames and manipulating the connection (e.g. by restricting the peer's congestion window size) so that RETIRECONNECTIONID frames can only be sent at a slower rate than they are received, leading to storage of…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-xhg9-xwch-vr7x
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2024-1410 Advisory: quiche vulnerable to unbounded storage of information related to connection ID retirement IDs: CVE-2024-1410, GHSA-xhg9-xwch-vr7x Record: https://patchnext.com/advisories/cve-2024-1410 (revision 1, source checked 26 Oct 2026, 15:38 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Low (CVSS 3.7) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: quiche 0.20.1, 0.19.2. A vendor fix does not mean a deployment is fixed. ## Affected components - crates.io quiche: affected < 0.19.2; >= 0.20.0, < 0.20.1; fixed in 0.20.1, 0.19.2 ## Suggested inspection (read-only) - crates.io quiche: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on quiche. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-xhg9-xwch-vr7x (GitHub-reviewed advisory GHSA-xhg9-xwch-vr7x lists affected ranges: crates.io quiche >=0 =0.20.0 <0.20.1) Commands are suggestions: review each one before running it.
Loading voting…