CVE-2024-1765
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 (through version 0.19.1/0.20.0) was affected by an unlimited resource allocation vulnerability causing rapid increase of memory usage of the system running quiche server or client. A remote attacker could take advantage of this vulnerability by repeatedly sending an unlimited number of 1-RTT CRYPTO frames after previously completing the QUIC handshake. Exploitation was possible for the duration of the connection which could be extended by the attacker. quiche 0.19.2 and 0.20.1 are the earliest versions containing the fix for this issue.
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 library (versions through 0.19.1/0.20.0) contains an unlimited resource allocation vulnerability where a remote attacker can cause rapid memory consumption by sending unlimited 1-RTT CRYPTO frames after completing the QUIC handshake. Since the attacker can extend the connection duration, memory usage grows unbounded until system resources are exhausted.
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< 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
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
-
Identify Quiche installationSearch for the quiche library in your system's installed packages, dependencies, or application code that links against quiche. Check package managers (npm, cargo, pip, etc.) or application dependency manifests for quiche.Affected if Cloudflare Quiche library is present in the environment
-
Check installed Quiche versionRun the package manager command to list the installed quiche version, or examine the Cargo.lock, package-lock.json, or equivalent dependency lock file for the quiche version entry.Affected if The installed version is less than 0.19.2 or exactly 0.20.0
-
Determine if QUIC server is enabledInspect the application or service configuration to see if it exposes a QUIC listener or endpoint using the quiche library for incoming connections.Affected if QUIC server functionality using quiche is enabled and accepting connections
-
Monitor for abnormal memory growthObserve process memory usage over time for any daemon or service that uses quiche. Use system monitoring tools to track memory consumption of QUIC-connected processes.Affected if Memory usage grows unbounded without bound as connection duration increases, indicating the vulnerability may be triggered
A system is affected if it runs Cloudflare Quiche version less than 0.19.2 or exactly 0.20.0 with QUIC server functionality enabled and accepting remote connections.
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 or 0.20.1 or later to patch the vulnerability. Consider implementing connection-level resource limits or monitoring for abnormal memory usage patterns as additional defense-in-depth measures.
Quiche 0.20.1 (or latest stable version, minimum 0.19.2)
- Identify the current Quiche version in use by checking project dependencies or Cargo.toml
- Upgrade Quiche to version 0.19.2 or higher (recommended: 0.20.1 or latest stable release)
- If using Cargo, update the dependency in Cargo.toml: quiche = "0.19.2" or quiche = "0.20.1"
- Run cargo update to fetch the new version
- Rebuild and redeploy the application
- Verify the fix by confirming the new version is active
Generated from the published advisory — verify against the referenced sources before acting.
- 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-1765 — 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-1765 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