Denial-of-Service in gRPC
Google gRPC
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| io.grpc:grpc-protobuf Maven |
|
|
| grpcio PyPI |
|
|
| grpc RubyGems |
Google gRPC
| Product | Affected | Fixed in |
|---|---|---|
| io.grpc:grpc-protobuf Maven |
|
|
| grpcio PyPI |
|
|
| grpc RubyGems |
≥ 1.51.0 · < 1.53.0
|
There exists an vulnerability causing an abort() to be called in gRPC. The following headers cause gRPC's C++ implementation to abort() when called via http2:
te: x (x != trailers)
:scheme: x (x != http, https)
grpclb_client_stats: x (x == anything)
On top of sending one of those headers, a later header must be sent that gets the total header size past 8KB. We recommend upgrading past git commit 2485fa94bd8a723e5c977d55a3ce10b301b437f8 or v1.53 and above.
From the CVE record · Google
gRPC’s C++ implementation can abort when it receives certain HTTP/2 headers followed by another header that pushes the total header size past 8 KB. An attacker able to send such headers can cause a denial of service; the input does not specify an authentication requirement or user interaction.
Teams running Google gRPC packages io.grpc:grpc-protobuf (Maven), grpcio (PyPI), or grpc (RubyGems) at versions 1.51.0 through versions before 1.53.0 should check their deployments.