Unbounded buffer accumulation in multipart header parsing causes denial of service in plug
elixir-plug plug
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| plug Hex |
|
|
elixir-plug plug
| Product | Affected | Fixed in |
|---|---|---|
| plug Hex |
|
|
1.18.21.19.2Allocation of Resources Without Limits or Throttling vulnerability in plug_project plug allows denial of service via unbounded buffer accumulation in multipart header parsing.
'Elixir.Plug.Conn':read_part_headers/2 in lib/plug/conn.ex does not obey its :length parameter. There is no upper bound on the size of the accumulated buffer. By contrast, the sibling function read_part_body has an explicit byte_size(acc) > length guard that stops accumulation once a limit is reached. No such guard exists in read_part_headers. An unauthenticated remote attacker can exhaust server memory by sending a crafted multipart/form-data request, causing a denial of service.
This issue affects plug from 1.4.0 before 1.15.4, 1.16.3, 1.17.1, 1.18.2, and 1.19.2.
From the CVE record · EEF
Plug's multipart header parser does not enforce its length limit, allowing unbounded buffer accumulation. An unauthenticated remote attacker can exhaust server memory and cause a denial of service with a crafted multipart/form-data request; no user interaction is needed.
Engineers running the Hex plug package should check versions >=1.4.0 <1.15.4, >=1.16.0 <1.16.3, >=1.17.0 <1.17.1, >=1.18.0 <1.18.2, and >=1.19.0 <1.19.2.