Skip to content
CVE PROGRAM SOURCE RECORD6.3 Medium

CVE-2024-7246

HPACK table poisoning in gRPC C++, Python & Ruby

Read JSON ↗CVE.org ↗
Status
Published
Published
Updated
Assigning organization
Google

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

Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.

Google gRPC

Default version status: unaffected

  • 1.53.0affected
  • 1.53.1affected
  • 1.53.2affected
  • 1.54.0affected
  • 1.54.1affected
  • 1.54.3affected
  • 1.55.0affected
  • 1.55.1affected
  • 1.55.3affected
  • 1.55.4affected
  • 1.56.0affected
  • 1.56.1affected
  • 1.56.2affected
  • 1.56.3affected
  • 1.56.4affected
  • 1.57.0affected
  • 1.57.1affected
  • 1.58.0affected
  • 1.58.1affected
  • 1.58.2affected
  • 1.59.0affected
  • 1.59.1affected
  • 1.59.2affected
  • 1.59.3affected
  • 1.59.4affected
  • 1.60.0affected
  • 1.60.1affected
  • 1.61.0affected
  • 1.61.1affected
  • 1.62.0affected
  • 1.61.2affected
  • 1.62.1affected
  • 1.62.2affected
  • 1.63.0affected
  • 1.63.1affected
  • 1.64.0affected
  • 1.64.1affected
  • 1.64.2affected
  • 1.65.0affected
  • 1.65.1affected
  • 1.65.2affected
  • 1.65.3affected

References