userTokenBalanceMap doesn't update when an user withdraws tokens from capitalPool
A user can withdraw his tokens from capitalPool using tokenManager:withdraw(), but the problem is it doesn't update the userTokenBalanceMap(which stores the withdrawable balance of the user) upon withdrawl
Malicious user can withdraw multiple times, completely draining the capitalPool
Manual Review
Reduce the userTokenBalanceMap to 0
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.