MyCut

AI First Flight #8
Beginner FriendlyFoundry
EXP
View results
Submission Details
Severity: high
Valid

Duplicate player addresses overwrite their reward in the `Pot` constructor, stranding funds and skewing `closePot`

Description


The constructor builds playersToRewardsby iterating the playersarray, but a player address that appears more than once simply overwrites the previous mapping entry, while i_players.length(used throughout closePot's math) still counts the duplicate slots.


for (uint256 i = 0; i < i_players.length; i++) {
playersToRewards[i_players[i]] = i_rewards[i]; // @> a duplicate address overwrites its earlier reward
}
```
​
So for a duplicated player the claimable amount collapses to only the **last** reward assigned, yet `totalRewards`/funding and `i_players.length` were sized as if each slot were a distinct allocation.
​
## Risk
​
**Likelihood: Medium**
​
- `createContest` does not de-duplicate or validate `players`, so a duplicate (by mistake or by a manager building the list programmatically) is accepted.
​
**Impact: High**
​
- The duplicated player can only ever claim one (the last) reward, not the sum of their entries, so part of the funded tokens allocated to them is unclaimable and becomes stranded. Simultaneously `closePot` divides by the inflated `i_players.length`, compounding the mis-distribution and the amount of funds left locked in the contract.
​
## Proof of Concept
​
```solidity
// players = [A, A, B], rewards = [100, 50, 70], totalRewards = 220 (funded)
// playersToRewards[A] = 100 then overwritten to 50; playersToRewards[B] = 70
// A can claim only 50 (not 150). 100 of the funded tokens are unallocated/stranded,
// and i_players.length = 3 skews closePot's claimantCut division.
```
​
## Recommended Mitigation
​
Reject duplicate players (and accumulate instead of overwrite if duplicates are ever intended):
​
```solidity
for (uint256 i = 0; i < players.length; i++) {
require(playersToRewards[players[i]] == 0, "duplicate player");
playersToRewards[players[i]] = rewards[i];
}
```
}
}
Updates

Lead Judging Commences

ai-first-flight-judge Lead Judge 7 days ago
Submission Judgement Published
Validated
Assigned finding tags:

[H-03] [M1] `Pot::constructor` Overwrites Rewards for Duplicate Players, Leading to Incorrect Distribution

## Description The `for` loop inside the `Pot::constructor` override the `playersToRewards[i_players[i]]` with new reward `i_rewards[i]`.So if a player's address appears multiple times, the reward is overwritten rather than accumulated. This results in the player receiving only the reward from the last occurrence of their address in the array, ignoring prior rewards. ## Vulnerability Details **Proof of Concept:** 1. Suppose i_players contains \[0x123, 0x456, 0x123] and i_rewards contains \[100, 200, 300]. 2. The playersToRewards mapping will be updated as follows during construction: - For address 0x123 at index 0, reward is set to 300. - For address 0x456 at index 1, reward is set to 200. - For address 0x123 at index 2, reward is updated to 100. 3. As a result, the final reward for address 0x123 in playersToRewards will be 100, not 400 (300+100).This leads to incorrect and lower reward distributions. **Proof of Code (PoC):** place the following in the `TestMyCut.t.sol::TestMyCut` ```Solidity address player3 = makeAddr("player3"); address player4 = makeAddr("player4"); address player5 = makeAddr("player5"); address[] sixPlayersWithDuplicateOneAddress = [player1, player2, player3, player4, player1, player5]; uint256[] rewardForSixPlayers = [2, 3, 4, 5, 6, 7]; uint256 totalRewardForSixPlayers = 27; // 2+3+4+5+6+7 function test_ConstructorFailsInCorrectlyAssigningReward() public mintAndApproveTokens { for (uint256 i = 0; i < sixPlayersWithDuplicateOneAddress.length; i++) { console.log("Player: %s reward: %d", sixPlayersWithDuplicateOneAddress[i], rewardForSixPlayers[i]); } /** * player1 has two occurance in sixPlayersWithDuplicateOneAddress ( at index 0 and 4) * So it's expected reward should be 2+6 = 8 */ vm.startPrank(user); contest = ContestManager(conMan).createContest(sixPlayersWithDuplicateOneAddress, rewardForSixPlayers, IERC20(ERC20Mock(weth)), totalRewardForSixPlayers); ContestManager(conMan).fundContest(0); vm.stopPrank(); uint256 expectedRewardForPlayer1 = rewardForSixPlayers[0] + rewardForSixPlayers[4]; uint256 assignedRewardForPlaye1 = Pot(contest).checkCut(player1); console.log("Expected Reward For Player1: %d", expectedRewardForPlayer1); console.log("Assigned Reward For Player1: %d", assignedRewardForPlaye1); assert(assignedRewardForPlaye1 < expectedRewardForPlayer1); } ``` ## Impact The overall integrity of the reward distribution process is compromised. Players with multiple entries in the i_players\[] array will only receive the reward from their last occurrence in the array, leading to incorrect and lower reward distributions. ## Recommendations **Recommended Mitigation:** Aggregate the rewards for each player inside the constructor to ensure duplicate addresses accumulate rewards instead of overwriting them.This can be achieved by using the += operator in the loop that assigns rewards to players. ```diff for (uint256 i = 0; i < i_players.length; i++) { - playersToRewards[i_players[i]] = i_rewards[i]; + playersToRewards[i_players[i]] += i_rewards[i]; } ```

Support

FAQs

Can't find an answer? Chat with us on Discord, Twitter or Linkedin.

Give us feedback!