GHSA-cfgp-2977-2fmm Connection confusion in gRPC

• Maven io.grpc:grpc-protobuf: >= 1.53.0, < 1.53.1 → fixed in 1.53.1 • PyPI grpcio: >= 1.53.0, < 1.53.1 → fixed in 1.53.1 • RubyGems grpc: >= 1.53.0, < 1.53.1 → fixed in 1.53.1 • PyPI grpcio: >= 1.54.0, < 1.54.2 → fixed in 1.54.2 • RubyGems grpc: >= 1.54.0, < 1.54.2 → fixed in 1.54.2 • Maven io.grpc:grpc-protobuf: >= 1.54.0, < 1.54.2 → fixed in 1.54.2

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.