Job argument injection via :args overrides primary_key and tenant in AshOban
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 0.8.14 and da2d81e1e8e1dcc3e6ec8587cdb4f273575ffca3.
Improperly Controlled Modification of Dynamically-Determined Object Attributes vulnerability in ash-project ash_oban allows a user whose input reaches the :args option of AshOban.build_trigger/3 to retarget an update or destroy trigger at another record, including across tenants. build_trigger/3 builds the trusted job arguments with atom keys (:primary_key, :tenant, :action_arguments) and merges the caller's :args underneath so the trusted values win on collision. Because Oban job arguments round-trip through JSON, the caller's keys arrive as strings, so Map.merge sees no collision and both keys survive. When the job is persisted the JSON object is de-duplicated keeping the last (string) key, and the worker reads the caller's value. The documentation describes :args as unable to affect the action, so an application that forwards user input into it for uniqueness scoping is exposed to authorization bypass and tenant isolation breaks. This issue affects ash_oban: from 0.2.5 before 0.8.14.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| ash-project | >=0.2.5 <0.8.14, >=ce079229ecdf0d323da2b554f30fc569e54660f0 <da2d81e1e8e1dcc3e6ec8587cdb4f273575ffca3 | 0.8.14, da2d81e1e8e1dcc3e6ec8587cdb4f273575ffca3 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket