Because calling the token manager's withdraw
function is always DOS'ed when the _tokenAddress
input is wrappedNativeToken
and the capital pool's wrappedNativeToken
allowance for the token manager is 0, such withdraw
function's caller can fail to claim the wrappedNativeToken
amount that is entitled to him in this situation.
When calling the following withdraw
function with the _tokenAddress
input being wrappedNativeToken
, _transfer(wrappedNativeToken, capitalPoolAddr, address(this), claimAbleAmount, capitalPoolAddr)
is executed.
In this case, when the capital pool's wrappedNativeToken
allowance for the token manager is 0, calling the following _transfer
function would execute ICapitalPool(_capitalPoolAddr).approve(address(this))
, where address(this)
is the address of the token manager.
However, calling the capital pool's following approve
function with the tokenAddr
input as the token manager's address would revert because calling such tokenAddr
's approve
function would fail. This causes the token manager's withdraw
function call to revert as well.
In this case, calling the token manager's withdraw
function would always be DOS'ed, which causes such withdraw
function's caller to fail to claim the wrappedNativeToken
amount that is entitled to him.
Manual Review
https://github.com/Cyfrin/2024-08-tadle/blob/c249cdb68c37c47025cdc4c4782c8ee3f20a5b98/src/core/TokenManager.sol#L247 can be updated to the following code.
If we consider the correct permissioned implementation for the `approve()` function within `CapitalPool.sol`, this would be a critical severity issue, because the withdrawal of funds will be permanently blocked and must be rescued by the admin via the `Rescuable.sol` contract, given it will always revert [here](https://github.com/Cyfrin/2024-08-tadle/blob/04fd8634701697184a3f3a5558b41c109866e5f8/src/core/CapitalPool.sol#L36-L38) when attempting to call a non-existent function selector `approve` within the TokenManager contract. The argument up in the air is since the approval function `approve` was made permisionless, the `if` block within the internal `_transfer()` function will never be invoked if somebody beforehand calls approval for the TokenManager for the required token, so the transfer will infact not revert when a withdrawal is invoked. I will leave open for escalation discussions, but based on my first point, I believe high severity is appropriate.
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.