When winnerIndex lands on a refunded slot, winner is set to
address(0). PuppyRaffle::selectWinner() then sends the prize
to address(0) — burning it permanently — before reverting on
_safeMint(address(0)) because OpenZeppelin ERC721 rejects
minting to the zero address. The entire transaction reverts,
leaving the raffle permanently stalled with no reset possible.
Likelihood:
Requires winnerIndex to land on a refunded slot
Probability proportional to fraction of zeroed slots
Combined with weak randomness bug — attacker can
deliberately trigger this to permanently stall the raffle
Impact:
Requires winnerIndex to land on a refunded slot
Probability proportional to fraction of zeroed slots
Combined with weak randomness bug — attacker can
deliberately trigger this to permanently stall the raffle
Attack Path:
10 players enter — contract holds 10 ETH
Attacker predicts winnerIndex using same formula
Attacker is the player at predicted index
Attacker calls refund() — their slot = address(0)
selectWinner() runs:
winner = players[winnerIndex] = address(0)
prizePool = 10 ETH * 80% = 8 ETH
winner.call{value: 8 ETH} → SUCCEEDS
(8 ETH burned to address(0) forever)
_safeMint(address(0)) → REVERTS
Transaction reverts — 8 ETH burned, raffle frozen
Add a zero address check for the winner before sending
the prize and minting the NFT. If winner is address(0),
skip that index and select the next valid player, or
revert with a clear error message to allow a new attempt.
## 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.