An airdrop claim is meant to be a one-time event per eligible address. The contract keeps mapping(address => bool) private s_hasClaimedSnowman for exactly that purpose, sets it during a successful claim, and exposes it through getClaimStatus.
claimSnowman never reads it. The flag is written at line 94 and the only other reference in the whole contract is the getClaimStatus view — so it constrains nothing. Compounding this, the signed struct is (receiver, amount) with no nonce, no deadline and no msg.sender binding, so one signature stays valid forever and anyone may submit it.
Likelihood:
Every time a whitelisted claimer re-acquires the snapshot balance and submits the same call again. Re-acquiring is cheap and intended: Snow::earnSnow hands out free Snow weekly and buySnow sells it on demand.
No signature refresh is needed. Because the digest is a pure function of (receiver, amount), the identical (v, r, s) tuple verifies on every replay.
claimSnowman does not constrain msg.sender, so any third party who has ever seen the signature can submit it.
Impact:
A single eligible address can mint the entire Snowman supply, amount NFTs per round, destroying the airdrop's distribution and the NFT's scarcity.
Because nothing binds msg.sender, a third party holding a once-valid signature can force the receiver's Snow to be staked and burned at a moment the receiver did not choose, using an authorisation the receiver believed was long consumed.
The receiver claims, re-buys the same balance, and replays the identical signature and proof for a second mint. Note the calls are made by the test contract, not the receiver — which also proves msg.sender is unconstrained.
Paste the harness and the test function into test/PoC.t.sol; put the test function inside contract PoC. Run forge test --match-path test/PoC.t.sol -vv.
Include the nonce and deadline in MESSAGE_TYPEHASH and in the struct hashed by getMessageHash, and increment s_nonces[receiver] on a successful claim.
# Root + Impact   **Root:** The [`claimSnowman`](https://github.com/CodeHawks-Contests/2025-06-snowman-merkle-airdrop/blob/b63f391444e69240f176a14a577c78cb85e4cf71/src/SnowmanAirdrop.sol#L44) function updates `s_hasClaimedSnowman[receiver] = true` but never checks if the user has already claimed before processing the claim, allowing users to claim multiple times if they acquire more Snow tokens. **Impact:** Users can bypass the intended one-time airdrop limit by claiming, acquiring more Snow tokens, and claiming again, breaking the airdrop distribution model and allowing unlimited NFT minting for eligible users. ## Description * **Normal Behavior:** Airdrop mechanisms should enforce one claim per eligible user to ensure fair distribution and prevent abuse of the reward system. * **Specific Issue:** The function sets the claim status to true after processing but never validates if `s_hasClaimedSnowman[receiver]` is already true at the beginning, allowing users to claim multiple times as long as they have Snow tokens and valid proofs. ## Risk **Likelihood**: Medium * Users need to acquire additional Snow tokens between claims, which requires time and effort * Users must maintain their merkle proof validity across multiple claims * Attack requires understanding of the missing validation check **Impact**: High * **Airdrop Abuse**: Users can claim far more NFTs than intended by the distribution mechanism * **Unfair Distribution**: Some users receive multiple rewards while others may receive none * **Economic Manipulation**: Breaks the intended scarcity and distribution model of the NFT collection ## Proof of Concept Add the following test to TestSnowMan.t.sol ```Solidity function testMultipleClaimsAllowed() public { // Alice claims her first NFT vm.prank(alice); snow.approve(address(airdrop), 1); bytes32 aliceDigest = airdrop.getMessageHash(alice); (uint8 v, bytes32 r, bytes32 s) = vm.sign(alKey, aliceDigest); vm.prank(alice); airdrop.claimSnowman(alice, AL_PROOF, v, r, s); assert(nft.balanceOf(alice) == 1); assert(airdrop.getClaimStatus(alice) == true); // Alice acquires more Snow tokens (wait for timer and earn again) vm.warp(block.timestamp + 1 weeks); vm.prank(alice); snow.earnSnow(); // Alice can claim AGAIN with new Snow tokens! vm.prank(alice); snow.approve(address(airdrop), 1); bytes32 aliceDigest2 = airdrop.getMessageHash(alice); (uint8 v2, bytes32 r2, bytes32 s2) = vm.sign(alKey, aliceDigest2); vm.prank(alice); airdrop.claimSnowman(alice, AL_PROOF, v2, r2, s2); // Second claim succeeds! assert(nft.balanceOf(alice) == 2); // Alice now has 2 NFTs } ``` ## Recommended Mitigation **Add a claim status check at the beginning of the function** to prevent users from claiming multiple times. ```diff // Add new error + error SA__AlreadyClaimed(); function claimSnowman(address receiver, bytes32[] calldata merkleProof, uint8 v, bytes32 r, bytes32 s) external nonReentrant { + if (s_hasClaimedSnowman[receiver]) { + revert SA__AlreadyClaimed(); + } + if (receiver == address(0)) { revert SA__ZeroAddress(); } // Rest of function logic... s_hasClaimedSnowman[receiver] = true; } ```
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.