Vulnerability in Google Grpc
CVE-2024-7246
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.
EPSS: 0.002 (12.7th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 5.3 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N.
Affected products
- Google Grpc — versions 1.53.0, 1.53.1, 1.53.2
- Grpc
Weakness classification (CWE)
Public proof-of-concept exploits
References
- cve-coordination@google.com (Exploit, Patch, Issue Tracking)
Frequently asked questions
- What is CVE-2024-7246?
- CVE-2024-7246 is a medium-severity vulnerability in Google Grpc, classified under Expected Behavior Violation. CVSS score: 5.3/10. Published 2024-08-06.
- How severe is CVE-2024-7246?
- Medium severity. CVSS v3 base score is 5.3 out of 10.
- Is CVE-2024-7246 known to be exploited?
- 3 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.