When user create an offer and cancel, user could withdraw their token with TokenManager's withdraw function.
But there is no approve token function call when _tokenAddress != wrappedNativeToken ( https://github.com/Cyfrin/2024-08-tadle/blob/04fd8634701697184a3f3a5558b41c109866e5f8/src/core/TokenManager.sol#L92 else case), It will occur wrong approve and user could not withdraw because it will occur Insufficient allowance with transfer.
In TokenManager.sol, there is withdraw function.
It call _safe_transfer_from function that will transfer token from capitalPoolAddr to msgSender().
But there is no approve before transfer token. It will occur an error so that user could not their token always.
This unit test code expect run successfully with withdraw function but it got fail.
Manual Review
We could fix withdraw function of TokenManager.sol like the below.
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.