Snowman Merkle Airdrop

AI First Flight #10
Beginner FriendlyFoundrySolidityNFT
EXP
View results
Submission Details
Severity: medium
Valid

getMessageHash() unconditionally reverts when the receiver holds zero Snow tokens, breaking the off-chain signature generation flow

Root + Impact

Description

The typical delegate-claim flow is:

  1. Receiver signs the SnowmanClaim digest off-chain (using getMessageHash())

  2. A relayer submits the claim on-chain via claimSnowman() with the signature

However, getMessageHash() reads the live balance and reverts if it is zero:

function getMessageHash(address receiver) public view returns (bytes32) {
// @> Reverts if receiver has no Snow — prevents pre-signing
if (i_snow.balanceOf(receiver) == 0) {
revert SA__ZeroAmount();
}
// @> Hash depends on live balance — changes every time balance changes
uint256 amount = i_snow.balanceOf(receiver);
return _hashTypedDataV4(
keccak256(abi.encode(MESSAGE_TYPEHASH, SnowmanClaim({receiver: receiver, amount: amount})))
);
}

Risk

Likelihood:

  • Any integration (frontend, script, or SDK) that calls getMessageHash() before the receiver holds tokens will receive a revert rather than a usable hash.

  • Any receiver whose balance changes between signing and claiming will find their pre-generated signature is now for the wrong digest.

Impact:

  • Off-chain relayer patterns and "sign now, claim later" UX flows are completely broken.

  • Frontends that pre-generate signatures for gasless UX will receive unexpected reverts.

Proof of Concept

function testGetMessageHashRevertsWithZeroBalance() public {
Helper helper = new Helper();
(SnowmanAirdrop airdrop,,, ) = helper.run();
address newUser = makeAddr("newUser");
// newUser has zero Snow tokens
// Cannot generate a signature hash — reverts
vm.expectRevert(SnowmanAirdrop.SA__ZeroAmount.selector);
airdrop.getMessageHash(newUser);
}

Recommended Mitigation

Accept the amount as an explicit parameter so the hash can be computed for any amount at any time, independent of the live balance:

function getMessageHash(address receiver, uint256 amount) public view returns (bytes32) {
if (amount == 0) revert SA__ZeroAmount();
return _hashTypedDataV4(
keccak256(abi.encode(
MESSAGE_TYPEHASH,
SnowmanClaim({receiver: receiver, amount: amount})
))
);
}
Updates

Lead Judging Commences

ai-first-flight-judge Lead Judge about 6 hours ago
Submission Judgement Published
Validated
Assigned finding tags:

[M-01] DoS to a user trying to claim a Snowman

# 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 ... } ```

Support

FAQs

Can't find an answer? Chat with us on Discord, Twitter or Linkedin.

Give us feedback!