Multipart form body parser bypasses body size limits in wisp
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 2.2.2 and *.
Allocation of Resources Without Limits or Throttling vulnerability in gleam-wisp wisp allows a denial of service via multipart form body parsing. The multipart_body function bypasses configured max_body_size and max_files_size limits. When a multipart boundary is not present in a chunk, the parser takes the MoreRequiredForBody path, which appends the chunk to the output but passes the quota unchanged to the recursive call. Only the final chunk containing the boundary is counted via decrement_quota. The same pattern exists in multipart_headers, where MoreRequiredForHeaders recurses without calling decrement_body_quota. An unauthenticated attacker can exhaust server memory or disk by sending arbitrarily large multipart form submissions in a single HTTP request. This issue affects wisp: from 0.2.0 before 2.2.2.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| gleam-wisp | wisp | >=0.2.0 <2.2.2 | 2.2.2 |
| gleam-wisp | =d8e722e22ccb42bda9d0b6248658d37ab4e9b376, >=0.2.0 <2.2.2 | *, 2.2.2 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket