CapitalPool::approve is called by TokenManager::_transfer or by anyone to give approval to TokenManager on the pool.
If TokenManager do not have the allowance, it calls the approve function but with its own address as a parameter.
As we can see in the approve function above, it won't work because the parameter should be the token to approve, not the TokenManager address. TokenManager do not have any approve function or is an ERC20 token, therefore it doesn't make any sense to use it as the argument.
Likelyhood: Low/Medium
Everytime a TokenManager is no allowance, that part of the code won't correct it as expected.
Impact: Low/Medium
Transfer won't work if approve is not called with the right token before _transfer.
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.