Memory exhaustion via unbounded deserialization of keyset pagination cursors in Ash.Page.Keyset
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 3.31.1 and 1816b103af975221210478d61db20adcea700319.
Uncontrolled Resource Consumption vulnerability in ash-project ash allows an attacker to exhaust the memory of the node via a crafted keyset pagination cursor. Read actions with keyset pagination deserialize the client-supplied page[:after] or page[:before] cursor in decode_values/2 in lib/ash/page/keyset.ex, which base64-decodes the value and passes it to :erlang.binary_to_term/2 without bounding its size. The Erlang external term format supports zlib-compressed payloads, which the decoder inflates transparently, so a cursor of a few kilobytes can allocate tens of megabytes of heap in a single call. Ash itself only ever encodes cursors uncompressed, so the decoder accepts a term shape its encoder never produces. Concurrent requests aggregate these allocations and can terminate the node. This issue affects ash: from 1.17.0 before 3.31.1.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| ash-hq | ash_framework | >=1.17.0 <3.31.1 | 3.31.1 |
| ash-project | >=1.17.0 <3.31.1, >=f8fadc67e67c955bb68b3a8d642be13e2b7e8ca9 <1816b103af975221210478d61db20adcea700319 | 3.31.1, 1816b103af975221210478d61db20adcea700319 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket