In the Puppy Raffle FirstFlight 1 contract, the refund function is intended to return a user's entrance fee and remove them from the active players list. However, it only updates the player's index to address(0) rather than removing the element and shrinking the array's .length.
The selectWinner function calculates the totalAmountCollected (and the subsequent 80% prizePool) by multiplying the static entranceFee by players.length. If any user has claimed a refund, the actual Ether balance of the contract will be less than the calculated totalAmountCollected. When selectWinner attempts to transfer the inflated prize pool to the winner, the transaction will revert due to an EVM OutOfFunds error.
Permanent Denial of Service (DoS): If even one user calls refund(), the selectWinner function becomes permanently deadlocked and will always revert.
Trapped Funds: Because the raffle can never be concluded, all remaining players' entrance fees, as well as the protocol's uncollected fees, are permanently locked inside the contract.
This test proves that a partial refund by just two players completely bricks the protocol's ability to select a winner:
Arrange: A group of players enters the raffle (handled by the playersToEnterInRaffle modifier), and the contract holds their pooled entrance fees.
Act: Two players (spider at index 0, and alice at index 1) call the refund() function. The contract correctly refunds their Ether, lowering the contract's actual balance, but fails to decrease the players array length.
Act: Time is fast-forwarded by 2 days (vm.warp) to bypass the raffleDuration lock.
Assert: spider attempts to call selectWinner(). The contract calculates a payout based on the original number of players, but because 2 players' worth of Ether has already left the contract, it cannot afford the payout. The vm.expectRevert() correctly catches the transaction crashing, proving the protocol is permanently broken.
The refund function must explicitly shrink the array when a user leaves the raffle. Implement the standard "Swap and Pop" pattern to keep the array length synchronized with the contract's actual balance:
## 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.