Skip to main content
Public proof of conceptFix available

CVE-2024-45311

A public proof of concept exists; no exploitation attested.

  • Published2024-09-02
  • Fixed in0.11.7 · 0.11.4
  • WeaknessCWE-670

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Quinn is a pure-Rust, async-compatible implementation of the IETF QUIC transport protocol. As of quinn-proto 0.11, it is possible for a server to `accept()`, `retry()`, `refuse()`, or `ignore()` an `Incoming` connection. However, calling `retry()` on an unvalidated connection exposes the server to a likely panic in the following situations: 1. Calling `refuse` or `ignore` on the resulting validated connection, if a duplicate initial packet is received. This issue can go undetected until a server's `refuse()`/`ignore()` code path is exercised, such as to stop a denial of service attack. 2. Accepting when the initial packet for the resulting validated connection fails to decrypt or exhausts connection IDs, if a similar initial packet that successfully decrypts and doesn't exhaust connection IDs is received. This issue can go undetected if clients are well-behaved. The former situation was observed in a real application, while the latter is only theoretical.

Timeline

dates in UTC
  1. 2024-09-0218:15CVE publishedNVD

Versions per branch

CISA-ADP · OSV · NVD
Quinn project quinn
BranchAffectedFixed in
0.11≥ 0.11.0, < 0.11.70.11.7
0.11≥ 0.11.0, < 0.11.40.11.4

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • quinn-rs quinn
    Affected
    • = >= 0.11.0, < 0.11.7no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2024-09-02

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • pixiWolfiall versions · fixed in 0.31.0-r0and 1 other package
  • pixiChainguardall versions · fixed in 0.31.0-r0and 1 other package
  • py3.10-uv-buildWolfiall versions · fixed in 0.4.7-r0and 9 other packages
  • py3.10-uv-buildChainguardall versions · fixed in 0.4.7-r0and 9 other packages
  • qdrantWolfiall versions · fixed in 1.11.3-r1and 2 other packages
  • qdrantChainguardall versions · fixed in 1.11.3-r1and 2 other packages
  • washWolfiall versions · fixed in 0.32.1-r1
  • washChainguardall versions · fixed in 0.32.1-r1

2 more package ranges on OSV.dev

Full record on NVD

Fix

  1. Update Quinn project quinn to 0.11.7 · 0.11.4

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • CISA-ADPSSVC decisionpoc2024-09-03
  • CNACVSS 3.17.5known since 2026-10-23
  • NVDCVSS 3.17.5read 2026-10-23
  • CNAweakness (CWE)CWE-670known since 2026-10-23
  • NVDweakness (CWE)CWE-670read 2026-10-23
  • FIRST EPSSEPSS score0.6 %2026-11-08
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryHIGH2024-09-03

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published
2024-09-02
Last Modified
2026-06-17
NVD status
Analyzed
GitHub Advisory
GHSA-vr26-jcq5-fjj8

Frequently asked questions

What is CVE-2024-45311?

Quinn is a pure-Rust, async-compatible implementation of the IETF QUIC transport protocol. As of quinn-proto 0.11, it is possible for a server to `accept()`, `retry()`, `refuse()`, or `ignore()` an `Incoming` connection. However, calling `retry()` on an unvalidated connection exposes the server to a likely panic in the following situations: 1. Calling `refuse` or `ignore` on the resulting validated connection, if a duplicate initial packet is received. This issue can go undetected until a server's `refuse()`/`ignore()` code path is exercised, such as to stop a denial of service attack. 2. Accepting when the initial packet for the resulting validated connection fails to decrypt or exhausts connection IDs, if a similar initial packet that successfully decrypts and doesn't exhaust connection IDs is received. This issue can go undetected if clients are well-behaved. The former situation was observed in a real application, while the latter is only theoretical.

Is CVE-2024-45311 actively exploited?

A proof-of-concept exploit exists for CVE-2024-45311, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2024-45311?

CVE-2024-45311 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Running quinn-proto? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record