Skip to content
6.3 Medium

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…

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.

Affected products and versions

Product Affected versions Fixed in
gRPC 1.65 1.65.0 → 1.65.3 No fix stated
gRPC 1.64 1.64.0 → 1.64.2 No fix stated
gRPC 1.63 1.63.0 → 1.63.1 No fix stated
gRPC 1.62 1.62.0 → 1.62.2 No fix stated
gRPC 1.61 1.61.0 → 1.61.2 No fix stated
gRPC 1.60 1.60.0 → 1.60.1 No fix stated
gRPC 1.59 1.59.0 → 1.59.4 No fix stated
gRPC 1.58 1.58.0 → 1.58.2 No fix stated
gRPC 1.57 1.57.0 → 1.57.1 No fix stated
Show the 4 other branches
Product Affected versions Fixed in
gRPC 1.56 1.56.0 → 1.56.4 No fix stated
gRPC 1.55 1.55.0 → 1.55.4 No fix stated
gRPC 1.54 1.54.0 → 1.54.3 No fix stated
gRPC 1.53 1.53.0 → 1.53.2 No fix stated

References

Timeline

  1. Published
  2. Last modified
The 6 CVEs of gRPC →
Track this CVE