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
| Package (Ecosystem) | Introduced | Fixed | Limit |
|---|---|---|---|
| io.grpc:grpc-protobuf(Maven) | 1.53.0 | 1.53.1 | N/A |
| grpcio(PyPI) | 1.53.0 | 1.53.1 | N/A |
| grpc(RubyGems) | 1.53.0 | 1.53.1 | N/A |
| grpcio(PyPI) | 1.54.0 | 1.54.2 | N/A |
| grpc(RubyGems) | 1.54.0 | 1.54.2 | N/A |
| io.grpc:grpc-protobuf(Maven) | 1.54.0 | 1.54.2 | N/A |
CVSS Metrics
