refund() introduces blank spots (address(0)) in the players array.
selectWinner() does not filter out inactive players.
Winner selection can resolve to address(0), causing mint and payout failures.
Because delete players; is executed after winner selection, a revert prevents reset, leaving the raffle stuck
The refund function sets refunded players to address(0) within the players array. During winner selection, the contract does not exclude these blank slots. If the random index points to a refunded slot, the raffle attempts to transfer ETH and mint an NFT to the zero address. Both operations revert, preventing the raffle from resetting and permanently bricking the protocol.
Likelihood:
High
Impact:
Prize ETH sent to address(0)
NFT minted to address(0) will lost forever
Raffle funds burned
Four players enter the raffle: [Alice, Bob, Carol, Dave].
Three players (Bob, Carol, Dave) call refund().
The players array becomes:
[0x0, 0x0, 0x0, Alice]
activePlayersCount is not tracked,
so players.length == 4.
Execution:
selectWinner() is called.
RNG selects winnerIndex = 0.
winner = players[0] = address(0).
Result:
ETH transfer to address(0) fails.
NFT mint to address(0) reverts.
Transaction reverts before delete players; executes.
Raffle state never resets → protocol permanently bricked
Use active player count
Skip zero address during winner selection
## 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.