Denial-of-Service 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 |
|
|
gRPC contains a vulnerability whereby a client can cause a termination of connection between a HTTP2 proxy and a gRPC server: a base64 encoding error for `-bin` suffixed headers will result in a disconnection by the gRPC server, but is typically allowed by HTTP2 proxies. We recommend upgrading beyond the commit in https://github.com/grpc/grpc/pull/32309 https://www.google.com/url
From the CVE record · Google
A client can cause a gRPC server to disconnect from an HTTP/2 proxy by sending a `-bin` suffixed header with invalid base64 encoding. HTTP/2 proxies typically allow the header, while the gRPC server disconnects; the input does not specify whether authentication is required.
Teams running 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.