Remote code execution and denial of service via unsafe Erlang term deserialization in elixir-grpc/grpc
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 1.0.0 and 272a97a5ea1b46af1819f14a831fcf35fc91f992.
Deserialization of Untrusted Data and Allocation of Resources Without Limits or Throttling vulnerabilities in elixir-grpc grpc allow unauthenticated attackers to crash the BEAM node via atom table exhaustion and, when a decoded term flows into a call site that invokes it, achieve remote code execution on the server. 'Elixir.GRPC.Codec.Erlpack':decode/2 (lib/grpc/codec/erlpack.ex) calls :erlang.binary_to_term/1 on the raw gRPC message body without the :safe option, no size bound, and no type guard. Any unauthenticated peer that sends a request with Content-Type: application/grpc+erlpack can send a crafted payload that mints arbitrary new atoms (which are never garbage-collected, exhausting the bounded atom table and crashing the VM) or that encodes a fun term which, if applied anywhere downstream, executes attacker-controlled code inside the server process. This issue affects grpc: from 0.4.0 before 1.0.0.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| elixir-grpc | >=0.4.0 <1.0.0, >=25bcc569fe2cc4478531a6c546c923205fc751c9 <272a97a5ea1b46af1819f14a831fcf35fc91f992 | 1.0.0, 272a97a5ea1b46af1819f14a831fcf35fc91f992 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket