Puppy Raffle

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

refund() replaces an index with address(0) which can cause selectWinner to always revert

Title: refund() replaces an index with address(0) which can cause selectWinner to always revert
Impact: High — Raffle permanently stuck after any refund.
Likelihood: High — Any refund triggers prize pool miscalculation.
Reference Files: src/PuppyRaffle.sol:103,131-133,151

Description:

Description

refund() creates array gaps by setting players[i] = address(0) without reducing the array length. selectWinner() multiplies players.length * entranceFee which counts refunded entries, inflating the prize pool beyond the actual contract balance. The vulnerable code:

players[playerIndex] = address(0); // gap, array.length UNCHANGED
uint256 totalAmountCollected = players.length * entranceFee;
uint256 prizePool = (totalAmountCollected * 80) / 100;
(bool success,) = winner.call{value: prizePool}("");

The call{value: prizePool} reverts because the contract holds less ETH than the calculated prize.

Risk

Impact: High. No winner can be selected. All funds permanently locked in the contract.
Likelihood: High. A single refund makes selectWinner() unrecoverable — it will always revert.
With 4 players, 1 refund reduces the balance to 3 ETH but prizePool is calculated as 3.2 ETH.

Proof of Concept

function testSelectWinnerRevertsAfterRefund() public {
address[] memory p = new address[](4);
p[0]=address(1); p[1]=address(2); p[2]=address(3); p[3]=address(4);
puppyRaffle.enterRaffle{value: entranceFee*4}(p);
vm.warp(block.timestamp + duration + 1);
vm.prank(address(4)); puppyRaffle.refund(3);
vm.expectRevert(); puppyRaffle.selectWinner();
}

After the refund, the prize pool calculation exceeds the contract balance, reverting every selectWinner() call.

Recommended Mitigation

Compact the array using swap-and-pop on refund:

players[playerIndex] = players[players.length - 1];
players.pop();

This keeps players.length equal to the number of active players, so totalAmountCollected matches the actual contract balance.

Updates

Lead Judging Commences

ai-first-flight-judge Lead Judge about 4 hours 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!