CVE-2024-7246
HPACK table poisoning in gRPC C++, Python & Ruby
Reported by google · Published August 6, 2024
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| grpc | Chainguard | 1.65.4-r0 |
| grpc-doc | Amazon Linux | 1.60.2-10.amzn2023 |
| grpc-cpp | Amazon Linux | 1.60.2-10.amzn2023 |
| grpc-devel | Amazon Linux | 1.60.2-10.amzn2023 |
| grpc | Amazon Linux | 1.60.2-10.amzn2023 |
| grpc-data | Amazon Linux | 1.60.2-10.amzn2023 |
| grpc | Wolfi | 1.65.4-r0 |
| grpc-plugins | Amazon Linux | 1.60.2-10.amzn2023 |
| grpc | grpc | 1.65.4, 1.64.3, 1.63.2, 1.62.3, 1.61.3, 1.60.2, 1.59.5, 1.58.3 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| gRPC | 1.53.0, 1.53.1, 1.53.2 | |
| gRPC | 1.64.2, 1.65.2, 1.65.0 | |
| chainguard | grpc | 0 |
| amazon:2023 | grpc-doc | 0 |
| amazon:2023 | grpc-cpp | 0 |
| amazon:2023 | grpc-devel | 0 |
| amazon:2023 | grpc | 0 |
| amazon:2023 | grpc-data | 0 |
| wolfi | grpc | 0 |
| amazon:2023 | grpc-plugins | 0 |
Timeline
- Aug 6, 2024 CVE Published
- Aug 6, 2024 CVE Updated
- Aug 13, 2024 EPSS Score (30 in total, the first dated here)
- Oct 5, 2024 Coalition ESS Score (7 in total, the first dated here)
- Jun 2, 2026 Security Advisory
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2024-7246
vulnetix vdb fixes CVE-2024-7246
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2024-7246/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart