Unbounded range expansion in cron describe causes memory exhaustion in oban_web
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 2.12.5 and 9998b7e284e02fdd4645dd6231760038e63b584d.
Uncontrolled Resource Consumption vulnerability in oban-bg oban_web (Oban.Web.CronExpr modules) allows memory exhaustion via unbounded cron range expansion. An attacker with access to schedule cron jobs can submit a malicious cron expression such as "0 0 1-100000000 * *". When a user with dashboard access views the cron job list, Oban.Web.CronExpr.describe/1 is called to render the expression. parse_range/2 parses both range endpoints via Integer.parse/1 with no bounds check, and the downstream helpers expand_dom_parts/1 and expand_dow_parts/1 materialise the range eagerly via Enum.to_list/1, causing allocation of ~2.4 GB and stalling or crashing the BEAM node. A sibling helper extract_dom_values already validates range bounds, but the expansion helpers do not. This issue affects oban_web: from 2.12.0 before 2.12.5.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| oban-bg | >=2.12.0 <2.12.5, >=a97c7960bb389b05aaab4cf8042985f02ceddc24 <9998b7e284e02fdd4645dd6231760038e63b584d | 2.12.5, 9998b7e284e02fdd4645dd6231760038e63b584d |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket