Elixir-grpc grpc_server
Streaming request body limit enforced only after an 8 MB read in elixir-grpc grpc_server
Allocation of Resources Without Limits or Throttling vulnerability in elixir-grpc grpc_server allows unauthenticated attackers to exhaust server memory via client-streaming or bidirectional-streaming requests. The streaming read clause of GRPC.Server.Adapters.Cowboy.Handler.info/3 (grpc_server/lib/grpc/server/adapters/cowboy/handler.ex) asks Cowboy for up to 8,000,000 bytes per read and compares the running total with max_body_size only after the read returns. The gRPC length prefix of a message is not checked before the message is buffered. Each stream can therefore buffer up to one full read beyond the configured limit before it is refused, and many concurrent streams exhaust node memory. Releases before 1.0.6 apply no limit to streaming requests at all. This issue affects grpc_server: from 1.0.0 before 1.1.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 1.0.0, < 1.1.0
Fixed in 1.1.0
- >= 49e18c3ec6bb9afe2f712caad3dbab5c56a68a00, < b1e771d558941b1ed4b6de8b39f6a5375543db01
Fixed in b1e771d558941b1ed4b6de8b39f6a5375543db01
Mitigation
Upgrade grpc_server to 1.1.0 or later.
Upgrade grpc_server to b1e771d558941b1ed4b6de8b39f6a5375543db01 or later.
References
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.