Title: Signature Invalidation (Griefing Attack) via Dynamic Balance Check in getMessageHash
Description: In the SnowMan Merkle AirDrop protocol, users can sign a message off-chain allowing a third party (a relayer) to claim a Snowman NFT on their behalf. The function getMessageHash(address receiver) constructs the cryptographic digest by dynamically querying the user's current token balance: uint256 amount = i_snow.balanceOf(receiver);.
Because the amount is dynamically pulled from the blockchain state at the time of execution rather than explicitly passed as a fixed parameter, it is vulnerable to a front-running griefing attack. If an attacker observes a valid claim transaction in the mempool, they can front-run it by transferring a tiny amount (even 1 wei) of Snow tokens to the receiver. This forcefully changes the receiver's balance.
When the victim's claim transaction executes, the contract recalculates the digest using the new balance. This causes ecrecover to return a completely invalid address, triggering an SA__InvalidSignature() revert and locking the user out of their claim.
Likelihood: Medium The attacker must actively monitor the mempool and spend a small amount of gas and tokens to execute the front-running attack.
Impact: High A successful attack completely prevents the receiver from claiming their NFT via delegation, acting as a permanent Denial of Service (DoS) for that specific signature.
Signature: Alice has 1 Snow token and signs a message off-chain to delegate her NFT claim.
Front-Run Attack: Bob monitors the mempool, spots the pending claim, and front-runs it by transferring 1 additional Snow token to Alice.
Execution & Revert: When the delegated claim transaction executes, the contract dynamically reads Alice's newly increased balance to calculate the hash. This mismatch instantly invalidates her original signature, reverting the transaction and permanently locking Alice out of her claim.
Remove the dynamic balanceOf query from the signature verification process. The amount to be claimed must be a static, explicit parameter passed into both getMessageHash and claimSnowman so that the user signs a fixed value that cannot be manipulated by outside state changes.
# 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.