Uncontrolled Recursion vulnerability in ash-project ashoban allows a user who can drive a trigger's onerror action to fail on the final attempt to exhaust worker CPU and memory, denying service.

The generated worker's atomic handleerror/4 runs the trigger's onerror action on a job's final attempt inside a rescue that, when the action itself raises, calls handleerror/4 again with the same job. The job's attempt still equals maxattempts, so it re-enters the same clause and re-runs the failing action, with no exit. Any deterministic onerror failure (a data-layer outage, a misconfigured action, or a record the action rejects) loops forever; because the recursive call is not in tail position, each iteration retains a formatted stacktrace and the process heap grows without bound while the failing statement is re-issued against the data layer until the runtime kills the worker.

This issue affects ashoban: from 0.8.0-rc.1 before 0.8.14.