First published: Tue Aug 06 2024(Updated: )
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.
Credit: cve-coordination@google.com
Affected Software | Affected Version | How to fix |
---|---|---|
gRPC | <1.58.3 | |
gRPC | >=1.59.0<=1.64.3 | |
gRPC | <1.65.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-7246 has been classified as a moderate severity vulnerability due to its potential to cause HTTP request failures and leak sensitive HTTP header keys.
To fix CVE-2024-7246, upgrade gRPC to versions 1.59.0 through 1.64.3 or any version after 1.65.4.
gRPC versions up to 1.58.3, between 1.59.0 and 1.64.3, and up to 1.65.4 are affected by CVE-2024-7246.
Potential attacks using CVE-2024-7246 include HPACK table poisoning and leakage of other clients' HTTP header keys.
Yes, CVE-2024-7246 can potentially lead to denial of service by causing failed requests for other clients.