A critical vulnerability in the TokenManager contract prevents users from withdrawing ERC20 tokens (other than WETH) from the CapitalPool due to the absence of an approval call. The use of _safe_transfer_from instead of the internal _transfer function results in a lack of necessary approval, causing a denial of service (DOS) for users attempting to withdraw funds.
Found in src/core/TokenManager.sol at Line 175
@>:
_safe_transfer_fromis used in case_tokenAddress != wrappedNativeTokeninstead of the internalTokenManager:_transfer, which has the necessaryapprovecall to the CapitalPool to grant transfering permission to the TokenManager. Without the approval via_transfer, it is impossible to draw ERC20 tokens from the CapitalPool and return those funds to the user.
Add following POC and run forge test -vvv --mt test_withdraw_ERC20_reverts
Result shows that the transaction failed with ERC20InsufficientAllowance
In the case of non-WETH withdrawals, users requests will be DOS-ed because the TokenManager is unable to transfer funds from the CapitalPool due to the lack of approval. This causes users to lose their funds.
Foundry Test
Use TokenManager:_transfer() at Line 233 instead of _safe_transfer_from() to ensure that the necessary approval is granted for transferring ERC20 tokens.
This issue's severity has similar reasonings to #252, whereby 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. Similarly, the argument here is the approval function `approve` was made permisionless, so if somebody beforehand calls approval for the TokenManager for the required token, 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. It also has a slightly different root cause and fix whereby an explicit approval needs to be provided before a call to `_safe_transfer_from()`, if not, the alternative `_transfer()` function should be used to provide an approval, assuming a fix was implemented for issue #252
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.