# CVE-2024-45311: Denial of service in quinn-proto when using `Endpoint::retry()`

> A remote attacker can cause a server panic and denial of service by sending specific duplicate or malformed initial packets to a QUIC server using the quinn-proto library.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Sep 2024
- **Updated:** 3 Sep 2024
- **Also known as:** GHSA-vr26-jcq5-fjj8, RUSTSEC-2024-0373

## What is CVE-2024-45311?

CVE-2024-45311 is a high-severity denial of service vulnerability in quinn-rs quinn, published on 2 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-670 (Always-Incorrect Control Flow Implementation)

## Which versions are affected by CVE-2024-45311?

3 open source packages ship an affected version, including quinn-proto. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `quinn-proto` | crates.io | From 0.11.0 | 0.11.7 |
| `quinn-proto` | crates.io | From 0.11.0 | 0.11.7 |
| `quinn-proto` | crates.io | From 0.11.0 | 0.11.7 |

Products: Quinn Project Quinn.

## How do I fix CVE-2024-45311?

Upgrade quinn-proto to 0.11.7 or later.

## Is CVE-2024-45311 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-45311 exists.

## Other vulnerabilities in quinn-rs quinn

- [CVE-2023-42805](https://insights.sbomify.com/CVE-2023-42805/): quinn-proto Denial of Service vulnerability (high 7.5)
- [CVE-2021-28036](https://insights.sbomify.com/CVE-2021-28036/): quinn invalidly assumes the memory layout of std::net::SocketAddr (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-45311 and fix it if it is affected.

What it is: CVE-2024-45311 is a high-severity denial of service vulnerability in quinn-rs quinn, published on 2 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-45311 exists.

Affected packages and fixed versions:
- quinn-proto (crates.io): affected from 0.11.0; fixed in 0.11.7
- quinn-proto (crates.io): affected from 0.11.0; fixed in 0.11.7
- quinn-proto (crates.io): affected from 0.11.0; fixed in 0.11.7

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-45311/ (Markdown: https://insights.sbomify.com/CVE-2024-45311/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-45311
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-45311
- OSV: https://osv.dev/vulnerability/CVE-2024-45311

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-45311/
Summaries are generated and may contain mistakes; the official description above is the record.