In ThrusterTreasure.sol, claimPrizesForRound() is a public function that allows users/winners to claim prizes. But this function doesnt satisfy the check-effect-interaction pattern and might become vulnerable to reentrancy if the external interactions allow callback functions.
Notably, claimPrizesForRound() will first call external interactions _claimPrize() which involves external token transfers in a for-loop. And it only updates users round info entered[msg.sender][roundToClaim] at the end of the function call. This means, if user can re-enter claimPrizesForRound(), users entered[msg.sender][roundToClaim] will not be cleared, potentially allowing users to _claimPrize() multiple times.
(https://github.com/code-423n4/2024-02-thruster/blob/3896779349f90a44b46f2646094cb34fffd7f66e/thruster-protocol/thruster-treasure/contracts/ThrusterTreasure.sol#L114-L118)
Update entered[msg.sender][roundToClaim] before calling _claimPrize().
