TokenManager:withdraw()
will revert if capitalPool hasn't given allowance before the call.
In TokenManager:withdraw()
, if the withdraw token is the wrappedNative (WETH), the _transfer()
function is called:
If the transfer comes from the capitalPool and the allowance hasn't been previously garanted the CapitalPool:approve()
function is called.
The issue is that, in TokenManager:_transfer()
, the call parameter is incorrectly set to address(this)
which is the TokenManagerProxy in this case.
As we can see, the CapitalPool:approve()
function accepts a ERC20 token as a parameter and then infitite-approves TokenManager for that token:
But, in this case, it is actually trying to call approve() on the proxy which doesn't have such function so the call simply reverts as we can see in the following foundry output:
If the allowance CapitalPool -> TokenManager isn't previously garanted the withdrawal will fail.
Fortunately, since CapitalPool:approve()
, is publicly exposed users can make the approve call themselves and fix the issue.
Add the following test inside PreMarkets.t.sol
:
Manual review
Foundry
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.