An attacker can withdraw the entire balance of the protocol because the map userTokenBalanceMap storing the balances of users is not updated at the end of withdraw function in TokenManager.sol
If we look at the function withdraw (https://github.com/Cyfrin/2024-08-tadle/blob/main/src/core/TokenManager.sol#L137-L189), it reads the user balance from the map userTokenBalanceMap and stores it in claimAbleAmount. But the mapping is never updated by reducing the claimAbleAmount from the map userTokenBalanceMap.
Loss of entire user funds held by the protocol.
Manual Review
Add the following line before the tokens are transferred to the caller to update the user balance held within the protocol.
userTokenBalanceMap[_accountAddress][_tokenAddress][_tokenBalanceType] -= claimAbleAmount;
Valid critical severity finding, the lack of clearance of the `userTokenBalanceMap` mapping allows complete draining of the CapitalPool contract. Note: This would require the approval issues highlighted in other issues to be fixed first (i.e. wrong approval address within `_transfer` and lack of approvals within `_safe_transfer_from` during ERC20 withdrawals)
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.