# CVE-2024-7246: HPACK table poisoning in gRPC C++, Python & Ruby

> Attackers can poison HPACK tables to leak HTTP header keys and cause request failures in gRPC clients communicating via HTTP/2 proxies.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Aug 2024
- **Updated:** 6 Aug 2024
- **Also known as:** AZL-47442, AZL-47571, BELL-CVE-2024-7246, DEBIAN-CVE-2024-7246, ECHO-776e-6420-85f8, GHSA-ghwg-gpp4-w4x3, OESA-2024-2064, UBUNTU-CVE-2024-7246

## What is CVE-2024-7246?

CVE-2024-7246 is a medium-severity vulnerability in Google gRPC, published on 6 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

It's possible for a gRPC client communicating with a HTTP/2 proxy to poison the HPACK table between the proxy and the backend such that other clients see failed requests. It's also possible to use this vulnerability to leak other clients HTTP header keys, but not values.

This occurs because the error status for a misencoded header is not cleared between header reads, resulting in subsequent (incrementally indexed) added headers in the first request being poisoned until cleared from the HPACK table.

Please update to a fixed version of gRPC as soon as possible. This bug has been fixed in 1.58.3, 1.59.5, 1.60.2, 1.61.3, 1.62.3, 1.63.2, 1.64.3, 1.65.4.

Weakness: CWE-440 (Expected Behavior Violation)

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

It affects 1 product.


Products: Grpc Grpc.

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

Upgrade to a fixed version.

## Is CVE-2024-7246 being exploited?

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

## Other vulnerabilities in Google gRPC

- [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-7246 and fix it if it is affected.

What it is: CVE-2024-7246 is a medium-severity vulnerability in Google gRPC, published on 6 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-7246 in the wild and no public exploit code.

Affected product: Google gRPC. 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-7246/ (Markdown: https://insights.sbomify.com/CVE-2024-7246/index.md)
```

## Sources

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

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