MyCut

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

Duplicate addresses in the players array overwrite rewards and inflate the closePot divisor, underpaying players and locking dust

Root + Impact

The Pot constructor is expected to give each listed player exactly the reward declared for them and to let closePot split the remaining pool among the actual players. It stores playersToRewards[player] = rewards[i] in a loop with no duplicate detection, so a repeated address keeps only the last reward; closePot then divides by the duplicate-inflated i_players.length, reducing every claimant cut and leaving a balance locked in the Pot.

for (uint256 i = 0; i < i_players.length; i++) {
@> playersToRewards[i_players[i]] = i_rewards[i]; // duplicate address overwrites the earlier reward
}
uint256 claimantCut = (remainingRewards - managerCut) / i_players.length; // divisor includes duplicates

Risk

Likelihood: Low. The owner lists the same address more than once when creating a contest; no validation rejects the duplicate.

Impact: Low. The duplicate-listed player can claim only the last reward, claimants receive less than their share because of the inflated divisor, and the under-distributed balance stays locked in the Pot.

Proof of Concept

Verified locally with forge 1.7.1 / solc 0.8.28 (one impersonation + one setup-only time-warp cheatcode):

function test_duplicatePlayersOverwriteAndInflateDivisor() public {
// players = [A, A], rewards = [40, 20], totalRewards = 60
cm.fundContest(0);
_claimAs(playerA, dupPot);
assertEq(token.balanceOf(playerA), 20); // overwritten: only the last reward
_advance90Days();
cm.closeContest(dupPot);
// claimantCut = (40 - 4) / players.length(2) = 18 instead of 36.
assertEq(token.balanceOf(playerA), 38);
assertEq(token.balanceOf(dupPot), 18); // dust locked by the inflated divisor
}

Recommended Mitigation

function createContest(address[] memory players, uint256[] memory rewards, IERC20 token, uint256 totalRewards)
public
onlyOwner
returns (address)
{
+ if (players.length == 0) revert ContestManager__EmptyPlayers();
+ if (players.length != rewards.length) revert ContestManager__LengthMismatch();
+ for (uint256 i = 0; i < players.length; i++) {
+ for (uint256 j = i + 1; j < players.length; j++) {
+ if (players[i] == players[j]) revert ContestManager__DuplicatePlayer();
+ }
+ }
Pot pot = new Pot(players, rewards, token, totalRewards);
Updates

Lead Judging Commences

ai-first-flight-judge Lead Judge about 3 hours 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!