Information leak in gRPC
Google gRPC
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| io.grpc:grpc-protobuf Maven |
|
|
| grpcio PyPI |
|
Google gRPC
| Product | Affected | Fixed in |
|---|---|---|
| io.grpc:grpc-protobuf Maven |
|
|
| grpcio PyPI |
|
|
| grpc RubyGems |
|
|
When gRPC HTTP2 stack raised a header size exceeded error, it skipped parsing the rest of the HPACK frame. This caused any HPACK table mutations to also be skipped, resulting in a desynchronization of HPACK tables between sender and receiver. If leveraged, say, between a proxy and a backend, this could lead to requests from the proxy being interpreted as containing headers from different proxy clients - leading to an information leak that can be used for privilege escalation or data exfiltration. We recommend upgrading beyond the commit contained in https://github.com/grpc/grpc/pull/33005 https://github.com/grpc/grpc/pull/33005
From the CVE record · Google
When an HTTP/2 header exceeds the size limit, gRPC can skip HPACK table updates and desynchronize the sender and receiver. Between a proxy and backend, this can cause requests to be interpreted with headers from other proxy clients, potentially enabling information disclosure, privilege escalation, or data exfiltration. The input does not specify whether authentication or user interaction is required.
Engineers using Maven io.grpc:grpc-protobuf, PyPI grpcio, or RubyGems grpc at versions >=1.53.0 <1.53.1 or >=1.54.0 <1.54.2 should check their deployments.