The batch
function in Batch.sol
uses delegatecall
to execute multiple calls in a single transaction, which could allow unintended state changes if arbitrary functions are executed. Without strict access control, this creates a risk of bypassing safeguards within each individual function.
The batch
function uses delegatecall
within a loop, allowing multiple state-altering functions to be called:
An attacker could exploit this by calling both deposit
and withdraw
in a single batch, potentially bypassing function-specific checks.
Exploiting batch processing could lead to:
Double-spending or bypassing individual function controls.
Manipulation of balances, causing financial discrepancies.
Manual code review
Restrict batch
calls to a whitelist of approved functions or add granular access control checks to prevent arbitrary function execution.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.