In TokenManager.sol, there is _transfer function. In this function, they call ICapitalPool approve function with wrong parameter. It requires token address, but they called address(this) -> tokenManager. It will occur wrong approve and user could not withdraw because it will occur Insufficient allowance with transfer.
In TokenManager.sol, there is _transfer function.
It calls ICapitalPool(_capitalPoolAddr).approve(address(this));
But CapitalPool's approve function require token address parameter, not token manager.
It will occur an error (Insufficient allowance with transfer) so that user could not withdraw their token.
This is the test code with withdraw.
It expect withdraw function run successfully, but it got fail.
Manual Review
We could fix _transfer function of TokenManager.sol like the below
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.