Streaming request body limit enforced only after an 8 MB read in elixir-grpc grpc_server
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| elixir-grpc | grpc_server | unaffected |
|
||||||
| elixir-grpc | grpc_server | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Elixir-grpc | Grpc Server |
|
||||||||
| Elixir-grpc | Grpc Server |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Streaming request body limit enforced only after an 8 MB read in elixir-grpc grpc_server | |
| First Time appeared |
Elixir-grpc
Elixir-grpc grpc Server |
|
| Weaknesses | CWE-770 | |
| CPEs | cpe:2.3:a:elixir-grpc:grpc_server:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Elixir-grpc
Elixir-grpc grpc Server |
|
| References |
|
|
| Metrics |
cvssV4_0
|