PuppyRaffle tracks players in a dynamic array and lets them exit via refund(), which zeroes their slot (players[playerIndex] = address(0)) but does not remove the entry from the array. The contract balance decreases by entranceFee for every refund issued.
selectWinner() computes totalAmountCollected = players.length * entranceFee, using the raw array length rather than the count of non-zero (active) entries. When one or more players have refunded, totalAmountCollected exceeds the ETH actually held by the contract, causing the winner transfer to attempt to send more ETH than exists and always revert — permanently blocking raffle completion.
Likelihood:
Any player who calls refund() before the raffle draw sets up the condition; a single refund among four players is enough to make prizePool exceed the contract balance and cause a permanent revert on selectWinner().
Impact:
The raffle draw is bricked for all remaining participants — their entrance fees are locked in the contract with no path to withdrawal (no admin rescue function exists), and the raffle can never conclude.
Three players enter the raffle, one refunds, and then selectWinner() is called after the duration elapses. The winner call reverts because prizePool (80% of 4 × entranceFee) exceeds the actual contract balance (3 × entranceFee).
The test confirms that a single refund before draw time permanently prevents selectWinner() from completing, trapping the remaining players' funds.
Track the count of active (non-refunded) entries separately and base prize pool calculations on that value rather than players.length.
Alternatively, maintain a separate activePlayerCount state variable that is incremented in enterRaffle and decremented in refund, eliminating the loop overhead.
## Description `PuppyRaffle::refund` is supposed to refund a player and remove him from the current players. But instead, it replaces his index value with address(0) which is considered a valid value by solidity. This can cause a lot issues because the players array length is unchanged and address(0) is now considered a player. ## Vulnerability Details ```javascript players[playerIndex] = address(0); @> uint256 totalAmountCollected = players.length * entranceFee; (bool success,) = winner.call{value: prizePool}(""); require(success, "PuppyRaffle: Failed to send prize pool to winner"); _safeMint(winner, tokenId); ``` If a player refunds his position, the function `PuppyRaffle::selectWinner` will always revert. Because more than likely the following call will not work because the `prizePool` is based on a amount calculated by considering that that no player has refunded his position and exit the lottery. And it will try to send more tokens that what the contract has : ```javascript uint256 totalAmountCollected = players.length * entranceFee; uint256 prizePool = (totalAmountCollected * 80) / 100; (bool success,) = winner.call{value: prizePool}(""); require(success, "PuppyRaffle: Failed to send prize pool to winner"); ``` However, even if this calls passes for some reason (maby there are more native tokens that what the players have sent or because of the 80% ...). The call will thankfully still fail because of the following line is minting to the zero address is not allowed. ```javascript _safeMint(winner, tokenId); ``` ## Impact The lottery is stoped, any call to the function `PuppyRaffle::selectWinner`will revert. There is no actual loss of funds for users as they can always refund and get their tokens back. However, the protocol is shut down and will lose all it's customers. A core functionality is exposed. Impact is high ### Proof of concept To execute this test : forge test --mt testWinnerSelectionRevertsAfterExit -vvvv ```javascript function testWinnerSelectionRevertsAfterExit() public playersEntered { vm.warp(block.timestamp + duration + 1); vm.roll(block.number + 1); // There are four winners. Winner is last slot vm.prank(playerFour); puppyRaffle.refund(3); // reverts because out of Funds vm.expectRevert(); puppyRaffle.selectWinner(); vm.deal(address(puppyRaffle), 10 ether); vm.expectRevert("ERC721: mint to the zero address"); puppyRaffle.selectWinner(); } ``` ## Recommendations Delete the player index that has refunded. ```diff - players[playerIndex] = address(0); + players[playerIndex] = players[players.length - 1]; + players.pop() ```
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.