The batchRedeemWToken function processes an array of redemption requests in a loop without limiting the size of _redeemWTokenArgs. This could allow an attacker to submit an excessively large array, causing the transaction to exceed the block gas limit and fail, potentially preventing legitimate batch redemptions.
Currently there's no limit on _redeemWTokenArgs.length: The function loops over all provided inputs, which can lead to excessive gas consumption.
The function does not lead to loss of funds but could disrupt protocol operations.
The issue affects usability rather than core security mechanisms.
The likelihood is High, as:
Any user can submit an excessively large batch request.
There is no built-in mechanism to prevent high gas consumption.
Implement a reasonable limit on _redeemWTokenArgs.length to prevent excessive gas consumption.
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.