Normal behavior: The enterRaffle function allows users to enter the raffle by providing a list of participant addresses and paying entranceFee * newPlayers.length. The function is expected to scale with the number of participants and reject only logically invalid entries such as duplicate addresses.
Issue: The function performs a quadratic (O(n²)) duplicate check over the entire players array after appending new entries. As the array grows, this check becomes increasingly expensive in gas, eventually making enterRaffle uncallable within realistic gas limits even when all provided addresses are unique. This creates a gas-based denial-of-service vector and imposes a hard scalability ceiling on the raffle.
Likelihood:
As the raffle accumulates participants over time, the gas cost of enterRaffle grows quadratically with the size of the players array, making the issue reachable during normal protocol usage.
An attacker or heavy user can intentionally submit large batches of unique addresses in early rounds, accelerating growth of the players array and pushing the function beyond feasible gas limits.
Impact:
Legitimate users may be unable to enter the raffle once the players array exceeds a certain size, effectively causing a denial of service for new participants.
The protocol becomes non-scalable and unreliable under realistic gas constraints, undermining its usability and fairness without requiring any invalid input or privileged access.
A Foundry test demonstrates a concrete scalability ceiling by enforcing a fixed per-call gas limit. With GAS_LIMIT = 8_000_000, enterRaffle succeeds when adding 75 unique participants but fails at 76 participants (out-of-gas), despite all addresses being unique. This confirms the DoS condition is gas-driven (not a logical revert) and is caused by the quadratic duplicate check over the growing players array.
Avoid O(n²) duplicate checks over an ever-growing array. Track uniqueness in O(1) using a mapping that records whether an address is already active in the current raffle. This both prevents duplicates and keeps enterRaffle scalable.
A minimal fix is to introduce mapping(address => bool) public isActivePlayer;:
set to true when a player enters,
set to false on refund,
clear/reset appropriately when the raffle round ends (e.g., when deleting players).
## Description `enterRaffle` function uses gas inefficient duplicate check that causes leads to Denial of Service, making subsequent participants to spend much more gas than previous users to enter. ## Vulnerability Details In the `enterRaffle` function, to check duplicates, it loops through the `players` array. As the `player` array grows, it will make more checks, which leads the later user to pay more gas than the earlier one. More users in the Raffle, more checks a user have to make leads to pay more gas. ## Impact As the arrays grows significantly over time, it will make the function unusable due to block gas limit. This is not a fair approach and lead to bad user experience. ## POC In existing test suit, add this test to see the difference b/w gas for users. once added run `forge test --match-test testEnterRaffleIsGasInefficient -vvvvv` in terminal. you will be able to see logs in terminal. ```solidity function testEnterRaffleIsGasInefficient() public { vm.startPrank(owner); vm.txGasPrice(1); /// First we enter 100 participants uint256 firstBatch = 100; address[] memory firstBatchPlayers = new address[](firstBatch); for(uint256 i = 0; i < firstBatchPlayers; i++) { firstBatch[i] = address(i); } uint256 gasStart = gasleft(); puppyRaffle.enterRaffle{value: entranceFee * firstBatch}(firstBatchPlayers); uint256 gasEnd = gasleft(); uint256 gasUsedForFirstBatch = (gasStart - gasEnd) * txPrice; console.log("Gas cost of the first 100 partipants is:", gasUsedForFirstBatch); /// Now we enter 100 more participants uint256 secondBatch = 200; address[] memory secondBatchPlayers = new address[](secondBatch); for(uint256 i = 100; i < secondBatchPlayers; i++) { secondBatch[i] = address(i); } gasStart = gasleft(); puppyRaffle.enterRaffle{value: entranceFee * secondBatch}(secondBatchPlayers); gasEnd = gasleft(); uint256 gasUsedForSecondBatch = (gasStart - gasEnd) * txPrice; console.log("Gas cost of the next 100 participant is:", gasUsedForSecondBatch); vm.stopPrank(owner); } ``` ## Recommendations Here are some of recommendations, any one of that can be used to mitigate this risk. 1. User a mapping to check duplicates. For this approach you to declare a variable `uint256 raffleID`, that way each raffle will have unique id. Add a mapping from player address to raffle id to keep of users for particular round. ```diff + uint256 public raffleID; + mapping (address => uint256) public usersToRaffleId; . . function enterRaffle(address[] memory newPlayers) public payable { require(msg.value == entranceFee * newPlayers.length, "PuppyRaffle: Must send enough to enter raffle"); for (uint256 i = 0; i < newPlayers.length; i++) { players.push(newPlayers[i]); + usersToRaffleId[newPlayers[i]] = true; } // Check for duplicates + for (uint256 i = 0; i < newPlayers.length; i++){ + require(usersToRaffleId[i] != raffleID, "PuppyRaffle: Already a participant"); - for (uint256 i = 0; i < players.length - 1; i++) { - for (uint256 j = i + 1; j < players.length; j++) { - require(players[i] != players[j], "PuppyRaffle: Duplicate player"); - } } emit RaffleEnter(newPlayers); } . . . function selectWinner() external { //Existing code + raffleID = raffleID + 1; } ``` 2. Allow duplicates participants, As technically you can't stop people participants more than once. As players can use new address to enter. ```solidity function enterRaffle(address[] memory newPlayers) public payable { require(msg.value == entranceFee * newPlayers.length, "PuppyRaffle: Must send enough to enter raffle"); for (uint256 i = 0; i < newPlayers.length; i++) { players.push(newPlayers[i]); } emit RaffleEnter(newPlayers); } ```
The contest is live. Earn rewards by submitting a finding.
Submissions are being reviewed by our AI judge. Results will be available in a few minutes.
View all submissionsThe contest is complete and the rewards are being distributed.