The TokenManager
transfer functions only verify the success of the call operation, which can lead to undetected transfer failures for tokens that return false instead of reverting
The transfer functions in the TokenTransfer
contract(inherited from Rescuable
) perform low-level calls to token contracts and only verify the success of the call operation. For example, in _safe_transfer_from
function:
As shown above, the function ONLY asserts the success of the call operation. However, some tokens do not revert on transfer failure; instead, they return false
. This flaw could result in a situation where a failed token transfer does not cause the transaction to revert
The same issue is present in the _safe_transfer
function.
Tokens that return false
on transfer failure will not trigger a transaction revert, leading to incorrect token balances tracking
Manual Review
Consider updating the transfer success check on the two mentioned functions above as follows:
I believe the issues and duplicates do not warrant low severity severity as even if the call to transfers returns false instead of reverting, there is no impact as it is arguably correct given there will be insufficient funds to perform a rescue/withdrawal. This will not affect `tillIn()` as there are explicit balance [checks that revert accordingly](https://github.com/Cyfrin/2024-08-tadle/blob/04fd8634701697184a3f3a5558b41c109866e5f8/src/core/TokenManager.sol#L255-L260) to prevent allowing creation of offers without posting the necessary collateral
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.