QuicheApplication · Cloudflare
CVE-2024-1410
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCloudflare 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCloudflare quiche suffers from an unbounded storage vulnerability in connection ID retirement processing. An unauthenticated remote attacker can send NEW_CONNECTION_ID frames while simultaneously restricting the victim's congestion window, causing RETIRE_CONNECTION_ID frames to be sent at a slower rate than new IDs are received. This creates an unbounded queue that leads to excessive memory/resource consumption.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
QuicheApplication
< 0.19.2= 0.20.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate quiche library in your environmentSearch for quiche in cargo dependencies (cargo.lock, Cargo.toml), system package manager listings, or application bundling. Quiche is a Rust QUIC library typically embedded in applications or services that handle QUIC traffic.Affected if quiche library is present in any form (direct dependency, transitive dependency, or bundled)
-
Identify the installed quiche versionRun 'cargo tree -p quiche' to see the exact version if using Cargo/Rust projects. For system packages, run 'dpkg -l | grep quiche' or 'rpm -qa | grep quiche'. Check Cargo.lock for the exact version string under [[package]] name="quiche".Affected if version cannot be determined or is not listed in a package manager
-
Compare version against affected rangesExamine the version found: versions below 0.19.2 (including any 0.18.x, 0.17.x, etc.) or exactly version 0.20.0 are vulnerable. The fixed versions are 0.19.2, 0.20.1, and later.Affected if installed version is less than 0.19.2 OR installed version equals exactly 0.20.0
You are affected if your environment uses the quiche library at a version less than 0.19.2 or exactly at version 0.20.0, and the system processes incoming QUIC connections where an attacker can send NEW_CONNECTION_ID frames.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.19.2
Upgrade quiche to version 0.19.2, 0.20.1, or later. No workaround exists for affected versions.
quiche version 0.20.1 (or 0.19.2 if staying on the 0.19.x branch)
- 1. Identify the currently installed quiche version by checking project dependencies or running `cargo list | grep quiche` if using Cargo
- 2. Stop any services or processes that depend on the affected quiche version
- 3. Update the quiche dependency in your project (e.g., in Cargo.toml) to version 0.20.1 or later: change `quiche = "0.20.0"` to `quiche = "0.20.1"`
- 4. Run `cargo update quiche` to fetch the fixed version
- 5. Rebuild the project with `cargo build` to ensure the new version compiles correctly
- 6. Restart the affected services with the newly built binaries
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Quiche
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1410 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-1410 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data