WebSocket fragmented message reassembly unbounded in bandit
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 1.11.0 and 21612c7c7b1ce43eccd36d3af3a2299d23513667.
Allocation of Resources Without Limits or Throttling vulnerability in mtrudel bandit allows unauthenticated remote denial of service via memory exhaustion. The fragment reassembly path in Bandit.WebSocket.Connection.handle_frame/3 in lib/bandit/websocket/connection.ex appends every incoming Continuation{fin: false} frame's payload to a per-connection iolist with no cumulative size cap. The existing max_frame_size option only bounds individual frames; a peer that streams an unbounded number of continuation frames without ever setting fin=1 grows BEAM heap linearly until the OS or a supervisor kills the process. Because the accumulation happens before WebSock.handle_in/2 is called, the application has no opportunity to interpose a size check. Phoenix Channels and LiveView both run over WebSock on Bandit, so a stock Phoenix application exposes this surface as soon as it accepts socket connections. This issue affects bandit: from 0.5.1 before 1.11.0.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| mtrudel | >=0.5.1 <1.11.0, >=8909391f486d42138c5308410bc5ea49a65f4d46 <21612c7c7b1ce43eccd36d3af3a2299d23513667 | 1.11.0, 21612c7c7b1ce43eccd36d3af3a2299d23513667 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket