userTokenBalanceMap
isn't updated in TokenManager.withdraw
, which results TokenManager.withdraw
can be called multiple times, by repeating calling the function, malicious user can steal all the tokens
In userTokenBalanceMap, the function doesn't update userTokenBalanceMap
after reading the values in TokenManager.sol#L141-L147.
userTokenBalanceMap
isn't updated in TokenManager.withdraw
, which results TokenManager.withdraw
can be called multiple times, by repeating calling the function, malicious user can steal all the tokens
VS code
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.