Puppy Raffle

AI First Flight #1
Beginner FriendlyFoundrySolidityNFT
EXP
View results
Submission Details
Severity: high
Valid

[Medium] selectWinner() puede elegir address(0) — raffle permanentemente atascado

Root + Impact

refund() leaves holes (address(0)) in the players[] array, and selectWinner() picks a random index over the full array including holes:

@> players[playerIndex] = address(0); // refund() - hole left in the array
@> uint256 winnerIndex = ... % players.length; // selectWinner() - may pick a hole

If winnerIndex lands on a hole, winner is address(0): winner.call{value: prizePool} succeeds (address(0) accepts ETH) so the prize is burned, and _safeMint(address(0), tokenId) reverts so the whole selectWinner() reverts. Impact: permanent DoS of the raffle - funds locked forever.

Description

Normal behavior: when the raffle ends, selectWinner() randomly picks one active player, sends them the prize pool and mints them the PuppyRaffle NFT.

The issue: a player who refunds leaves a permanent hole in the array. When selectWinner() is called, if the random index points at the hole, the transaction reverts. Since the index is a pure function of block values, an attacker can simply wait for a block where the index hits the hole and keep calling - or the legitimate caller eventually hits it. The raffle can never complete: prize and all entrance fees stay locked forever (players can only self-refund).

Risk

Reason 1: array holes are never compacted and remain in players.length.
Reason 2: _safeMint to address(0) reverts, blocking winner payout.

Impact 1: permanent DoS of the raffle - funds locked forever.
Impact 2: prize pool burned to address(0) if the call succeeds first (in variants without the mint revert).

Proof of Concept

// 4 players enter; alice refunds - players[0] == address(0)
vm.prank(alice);
raffle.refund(0);
// force winnerIndex = 0 (the hole)
vm.warp(block.timestamp + 86400);
vm.prevrandao(0);
vm.expectRevert();
raffle.selectWinner(); // reverts forever

Forge test test_BUG3_refundedSlotCanBlockRaffle PASS: selectWinner() reverts, raffle permanently stuck.

Recommended Mitigation

Compacting the array on refund (move last element into the hole and pop), or skip zero-address winners in selectWinner(), or disallow refunding.

Updates

Lead Judging Commences

ai-first-flight-judge Lead Judge 1 day ago
Submission Judgement Published
Validated
Assigned finding tags:

[H-04] `PuppyRaffle::refund` replaces an index with address(0) which can cause the function `PuppyRaffle::selectWinner` to always revert

## 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() ```

Support

FAQs

Can't find an answer? Chat with us on Discord, Twitter or Linkedin.

Give us feedback!