Unbounded request body accumulation causes memory exhaustion in elixir-grpc/grpc
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 1.0.0 and 49e18c3ec6bb9afe2f712caad3dbab5c56a68a00.
Allocation of Resources Without Limits or Throttling vulnerability in elixir-grpc grpc allows unauthenticated attackers to exhaust the BEAM's memory and crash the server by streaming a large or slow-trickle unary request body. 'Elixir.GRPC.Server.Adapters.Cowboy.Handler':read_full_body/3 (lib/grpc/server/adapters/cowboy/handler.ex) accumulates every received chunk into a single growing binary with no size cap. Additionally, when the client omits the grpc-timeout header, the per-chunk read timeout resolves to :infinity, allowing a slow-trickle client to keep the connection alive indefinitely while memory grows. A single connection is sufficient to exhaust server memory and crash the node. This issue affects grpc: from 0.3.0-alpha.2 before 1.0.0.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| elixir-grpc | >=0.3.0-alpha.2 <1.0.0, >=d1abe70a6cad6dac4a3f8235d883d7c896989560 <49e18c3ec6bb9afe2f712caad3dbab5c56a68a00 | 1.0.0, 49e18c3ec6bb9afe2f712caad3dbab5c56a68a00 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket