# CVE-2024-11407: Denial of Service through Data corruption in gRPC-C++

> Attackers can cause denial of service in gRPC-C++ servers by triggering data corruption when zero-copy transmission is enabled.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H/S:N/AU:N/R:A/RE:L/U:Green`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 26 Nov 2024
- **Updated:** 26 Nov 2024
- **Also known as:** AZL-53456, BELL-CVE-2024-11407, DEBIAN-CVE-2024-11407, ECHO-f4e8-dde8-d71e, GHSA-p9rf-64qj-22rw, OESA-2024-2573, RHSA-2025:1019, UBUNTU-CVE-2024-11407

## What is CVE-2024-11407?

CVE-2024-11407 is a medium-severity denial of service vulnerability in gRPC-C++, published on 26 Nov 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

There exists a denial of service through Data corruption in gRPC-C++ - gRPC-C++ servers with transmit zero copy enabled through the channel arg GRPC_ARG_TCP_TX_ZEROCOPY_ENABLED can experience data corruption issues. The data sent by the application may be corrupted before transmission over the network thus leading the receiver to receive an incorrect set of bytes causing RPC requests to fail. We recommend upgrading past commit e9046b2bbebc0cb7f5dc42008f807f6c7e98e791

Weakness: CWE-682 (Incorrect Calculation)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `python-grpcio` | Red Hat:satellite:6.16::el8 | All versions | 0:1.68.1-1.el8pc |
| `python-grpcio-debugsource` | Red Hat:satellite:6.16::el8 | All versions | 0:1.68.1-1.el8pc |
| `python3.11-grpcio` | Red Hat:satellite:6.16::el8 | All versions | 0:1.68.1-1.el8pc |
| `python3.11-grpcio-debuginfo` | Red Hat:satellite:6.16::el8 | All versions | 0:1.68.1-1.el8pc |
| `python-grpcio` | Red Hat:satellite:6.16::el9 | All versions | 0:1.68.1-1.el9pc |
| `python-grpcio-debugsource` | Red Hat:satellite:6.16::el9 | All versions | 0:1.68.1-1.el9pc |
| `python3.11-grpcio` | Red Hat:satellite:6.16::el9 | All versions | 0:1.68.1-1.el9pc |
| `python3.11-grpcio-debuginfo` | Red Hat:satellite:6.16::el9 | All versions | 0:1.68.1-1.el9pc |
| `python-grpcio` | Red Hat:satellite_capsule:6.16::el8 | All versions | 0:1.68.1-1.el8pc |
| `python-grpcio-debugsource` | Red Hat:satellite_capsule:6.16::el8 | All versions | 0:1.68.1-1.el8pc |
| `python3.11-grpcio` | Red Hat:satellite_capsule:6.16::el8 | All versions | 0:1.68.1-1.el8pc |
| `python3.11-grpcio-debuginfo` | Red Hat:satellite_capsule:6.16::el8 | All versions | 0:1.68.1-1.el8pc |
| `python-grpcio` | Red Hat:satellite_capsule:6.16::el9 | All versions | 0:1.68.1-1.el9pc |
| `python-grpcio-debugsource` | Red Hat:satellite_capsule:6.16::el9 | All versions | 0:1.68.1-1.el9pc |
| `python3.11-grpcio` | Red Hat:satellite_capsule:6.16::el9 | All versions | 0:1.68.1-1.el9pc |
| `python3.11-grpcio-debuginfo` | Red Hat:satellite_capsule:6.16::el9 | All versions | 0:1.68.1-1.el9pc |

Products: Grpc Grpc.

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

Upgrade to a fixed version.

## Is CVE-2024-11407 being exploited?

There is no known exploitation of CVE-2024-11407 in the wild and no public exploit code.

## Other vulnerabilities in gRPC-C++

- [CVE-2017-9431](https://insights.sbomify.com/CVE-2017-9431/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-8359](https://insights.sbomify.com/CVE-2017-8359/): Use after free in n/a (critical 9.8)
- [CVE-2017-7860](https://insights.sbomify.com/CVE-2017-7860/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-7861](https://insights.sbomify.com/CVE-2017-7861/): Memory corruption in n/a (critical 9.8)
- [CVE-2026-33186](https://insights.sbomify.com/CVE-2026-33186/): gRPC-Go has an authorization bypass via missing leading slash in :path (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-11407 is a medium-severity denial of service vulnerability in gRPC-C++, published on 26 Nov 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-11407 in the wild and no public exploit code.

Affected product: gRPC-C++. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-11407/ (Markdown: https://insights.sbomify.com/CVE-2024-11407/index.md)
```

## Sources

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

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