Anyone can permanently block a specific user from claiming their Snowman NFT by sending them 1 wei of the Snow token, causing the claim transaction to always revert.
Normally, users claim their Snowman NFT by providing a valid Merkle proof and a signature that matches their address and current Snow token balance. The contract calculates the amount from the user's live token balance, then uses it to verify both the signature and the Merkle proof.
The problem is that the claim function uses i_snow.balanceOf(receiver) to determine the amount for both the signature verification and the Merkle leaf calculation. Because anyone can transfer arbitrary amounts of Snow tokens to any address, an attacker can slightly alter a victim's balance before they claim. This changes the amount used in the signature digest and Merkle leaf, causing both verifications to fail permanently.
Likelihood:High
This will occur every time an attacker sends any positive amount of Snow tokens to a user who hasn't claimed yet
The attack requires only a single transaction with negligible cost (1 wei)
Any user with a non-zero Snow balance is a potential victim
Impact:High
The victim is permanently unable to claim their Snowman NFT
The attacker does not profit financially, but griefs the victim effectively (Griefing DoS)
The victim's Snow tokens remain locked in their wallet (the contract never pulls them)
No way to recover unless the contract is redeployed with a new Merkle root
MockSnow: A simple ERC20 contract with an additional mint function for distributing tokens in the test.
MockSnowman: An ERC721 contract with a mintSnowman function that performs NFT manipulation (ignoring the amount for simplicity).
The test proceeds as follows: approvals, signatures, attack, Alice's failed attempt (due to a signature error), Bob's success, and final verification.
Pass the claim amount as a parameter and verify it against the Merkle root instead of using the live balanceOf. The signature should also commit to this amount.
# Root + Impact ## Description * Users will approve a specific amount of Snow to the SnowmanAirdrop and also sign a message with their address and that same amount, in order to be able to claim the NFT * Because the current amount of Snow owned by the user is used in the verification, an attacker could forcefully send Snow to the receiver in a front-running attack, to prevent the receiver from claiming the NFT.  ```Solidity function getMessageHash(address receiver) public view returns (bytes32) { ... // @audit HIGH An attacker could send 1 wei of Snow token to the receiver and invalidate the signature, causing the receiver to never be able to claim their Snowman uint256 amount = i_snow.balanceOf(receiver); return _hashTypedDataV4( keccak256(abi.encode(MESSAGE_TYPEHASH, SnowmanClaim({receiver: receiver, amount: amount}))) ); ``` ## Risk **Likelihood**: * The attacker must purchase Snow and forcefully send it to the receiver in a front-running attack, so the likelihood is Medium **Impact**: * The impact is High as it could lock out the receiver from claiming forever ## Proof of Concept The attack consists on Bob sending an extra Snow token to Alice before Satoshi claims the NFT on behalf of Alice. To showcase the risk, the extra Snow is earned for free by Bob. ```Solidity function testDoSClaimSnowman() public { assert(snow.balanceOf(alice) == 1); // Get alice's digest while the amount is still 1 bytes32 alDigest = airdrop.getMessageHash(alice); // alice signs a message (uint8 alV, bytes32 alR, bytes32 alS) = vm.sign(alKey, alDigest); vm.startPrank(bob); vm.warp(block.timestamp + 1 weeks); snow.earnSnow(); assert(snow.balanceOf(bob) == 2); snow.transfer(alice, 1); // Alice claim test assert(snow.balanceOf(alice) == 2); vm.startPrank(alice); snow.approve(address(airdrop), 1); // satoshi calls claims on behalf of alice using her signed message vm.startPrank(satoshi); vm.expectRevert(); airdrop.claimSnowman(alice, AL_PROOF, alV, alR, alS); } ``` ## Recommended Mitigation Include the amount to be claimed in both `getMessageHash` and `claimSnowman` instead of reading it from the Snow contract. Showing only the new code in the section below ```Python function claimSnowman(address receiver, uint256 amount, bytes32[] calldata merkleProof, uint8 v, bytes32 r, bytes32 s) external nonReentrant { ... bytes32 leaf = keccak256(bytes.concat(keccak256(abi.encode(receiver, amount)))); if (!MerkleProof.verify(merkleProof, i_merkleRoot, leaf)) { revert SA__InvalidProof(); } // @audit LOW Seems like using the ERC20 permit here would allow for both the delegation of the claim and the transfer of the Snow tokens in one transaction i_snow.safeTransferFrom(receiver, address(this), amount); // send ... } ```
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.