Santa's List

AI First Flight #3
Beginner FriendlyFoundry
EXP
View results
Submission Details
Severity: high
Valid

buyPresent burns the receiver's SantaTokens and mints the NFT to the caller, letting anyone steal others' tokens for a free NFT

Description

SantasList::buyPresent is meant to let a caller spend their own SantaToken to mint an NFT for someone else (presentReceiver). Instead it inverts both the payer and the recipient:

function buyPresent(address presentReceiver) external {
@> i_santaToken.burn(presentReceiver); // burns the RECEIVER's tokens, not the caller's
@> _mintAndIncrement(); // mints the NFT to msg.sender, not the receiver
}

_mintAndIncrement always mints to msg.sender, and SantaToken::burn(from) burns a fixed 1e18 from from with only an "is caller the SantasList contract" check — there is no allowance or ownership check on from:

function burn(address from) external {
if (msg.sender != i_santasList) { revert SantaToken__NotSantasList(); }
_burn(from, 1e18);
}

Because buyPresent passes presentReceiver straight into burn, any caller can burn any other address's SantaToken balance while receiving the NFT themselves — the caller pays nothing and the named "receiver" both loses tokens and gets no NFT.

Risk

Likelihood: High

  • Any address can call buyPresent(victim) for any victim that holds at least 1e18 SantaToken; no approval, ownership, or list status is required.

  • SantaToken::burn performs no allowance check, so nothing stops a third party from spending someone else's tokens through this path.

Impact: High

  • An attacker permanently destroys a victim's earned SantaToken balance without consent and mints the NFT to themselves for free, repeating it to drain every eligible victim.

  • This breaks two core invariants: a present must be paid for by its buyer, and a user's SantaToken balance can only be spent by that user.

Proof of Concept

Add to test/unit/SantasListTest.t.sol. Santa marks a victim EXTRA_NICE so the victim legitimately earns 1e18 SantaToken by collecting; an unrelated attacker then burns those tokens and takes an NFT for free.

function testBuyPresentStealsVictimTokensAndNft() public {
address victim = makeAddr("victim");
address attacker = makeAddr("attacker");
// Santa makes victim EXTRA_NICE so victim can earn a SantaToken
vm.startPrank(santa);
santasList.checkList(victim, SantasList.Status.EXTRA_NICE);
santasList.checkTwice(victim, SantasList.Status.EXTRA_NICE);
vm.stopPrank();
vm.warp(santasList.CHRISTMAS_2023_BLOCK_TIME());
vm.prank(victim);
santasList.collectPresent();
assertEq(santaToken.balanceOf(victim), 1e18);
// Attacker owns nothing and is on no list
assertEq(santaToken.balanceOf(attacker), 0);
assertEq(santasList.balanceOf(attacker), 0);
// Attacker calls buyPresent(victim): burns victim's tokens, mints NFT to attacker
vm.prank(attacker);
santasList.buyPresent(victim);
// Victim's tokens destroyed without consent...
assertEq(santaToken.balanceOf(victim), 0);
// ...and attacker received the NFT for free
assertEq(santasList.balanceOf(attacker), 1);
}

Run: forge test --mt testBuyPresentStealsVictimTokensAndNft — it passes, proving the theft.

Recommended Mitigation

Charge the caller and deliver the NFT to the receiver, so payer and recipient match the intended semantics:

function buyPresent(address presentReceiver) external {
- i_santaToken.burn(presentReceiver);
- _mintAndIncrement();
+ // The caller pays with their own tokens...
+ i_santaToken.burn(msg.sender);
+ // ...and the present (NFT) is minted to the intended receiver.
+ _safeMint(presentReceiver, s_tokenCounter++);
}

burn(msg.sender) ensures only the caller's own balance can be spent, and minting to presentReceiver delivers the NFT to the intended party. Separately, note that burn destroys 1e18 while the documented PURCHASED_PRESENT_COST is 2e18; align the burned amount with the intended cost.

Updates

Lead Judging Commences

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

[H-03] SantasList::buyPresent burns token from presentReceiver instead of caller and also sends present to caller instead of presentReceiver.

## Description The `buyPresent` function sends the present to the `caller` of the function but burns token from `presentReceiver` but the correct method should be the opposite of it. Due to this implementation of the function, malicious caller can mint NFT by burning the balance of other users by passing any arbitrary address for the `presentReceiver` field and tokens will be deducted from the `presentReceiver` and NFT will be minted to the malicious caller. Also, the NatSpec mentions that one has to approve `SantasList` contract to burn their tokens but it is not required and even without approving the funds can be burnt which means that the attacker can burn the balance of everyone and mint a large number of NFT for themselves. `buyPresent` function should send the present (NFT) to the `presentReceiver` and should burn the SantaToken from the caller i.e. `msg.sender`. ## Vulnerability Details The vulnerability lies inside the SantasList contract inside the `buyPresent` function starting from line 172. The buyPresent function takes in `presentReceiver` as an argument and burns the balance from `presentReceiver` instead of the caller i.e. `msg.sender`, as a result of which an attacker can specify any address for the `presentReceiver` that has approved or not approved the SantasToken (it doesn't matter whether they have approved token or not) to be spent by the SantasList contract, and as they are the caller of the function, they will get the NFT while burning the SantasToken balance of the address specified in `presentReceiver`. This vulnerability occurs due to wrong implementation of the buyPresent function instead of minting NFT to presentReceiver it is minted to caller as well as the tokens are burnt from presentReceiver instead of burning them from `msg.sender`. Also, the NatSpec mentions that one has to approve `SantasList` contract to burn their tokens but it is not required and even without approving the funds can be burnt which means that the attacker can burn the balance of everyone and mint a large number of NFT for themselves. ```cpp /* * @notice Buy a present for someone else. This should only be callable by anyone with SantaTokens. * @dev You'll first need to approve the SantasList contract to spend your SantaTokens. */ function buyPresent(address presentReceiver) external { @> i_santaToken.burn(presentReceiver); @> _mintAndIncrement(); } ``` ## PoC Add the test in the file: `test/unit/SantasListTest.t.sol` Run the test: ```cpp forge test --mt test_AttackerCanMintNft_ByBurningTokensOfOtherUsers ``` ```cpp function test_AttackerCanMintNft_ByBurningTokensOfOtherUsers() public { // address of the attacker address attacker = makeAddr("attacker"); vm.startPrank(santa); // Santa checks user once as EXTRA_NICE santasList.checkList(user, SantasList.Status.EXTRA_NICE); // Santa checks user second time santasList.checkTwice(user, SantasList.Status.EXTRA_NICE); vm.stopPrank(); // christmas time 🌳🎁 HO-HO-HO vm.warp(santasList.CHRISTMAS_2023_BLOCK_TIME()); // User collects their NFT and tokens for being EXTRA_NICE vm.prank(user); santasList.collectPresent(); assertEq(santaToken.balanceOf(user), 1e18); uint256 attackerInitNftBalance = santasList.balanceOf(attacker); // attacker get themselves the present by passing presentReceiver as user and burns user's SantaToken vm.prank(attacker); santasList.buyPresent(user); // user balance is decremented assertEq(santaToken.balanceOf(user), 0); assertEq(santasList.balanceOf(attacker), attackerInitNftBalance + 1); } ``` ## Impact - Due to the wrong implementation of function, an attacker can mint NFT by burning the SantaToken of other users by passing their address for the `presentReceiver` argument. The protocol assumes that user has to approve the SantasList in order to burn token on their behalf but it will be burnt even though they didn't approve it to `SantasList` contract, because directly `_burn` function is called directly by the `burn` function and both of them don't check for approval. - Attacker can burn the balance of everyone and mint a large number of NFT for themselves. ## Recommendations - Burn the SantaToken from the caller i.e., `msg.sender` - Mint NFT to the `presentReceiver` ```diff + function _mintAndIncrementToUser(address user) private { + _safeMint(user, s_tokenCounter++); + } function buyPresent(address presentReceiver) external { - i_santaToken.burn(presentReceiver); - _mintAndIncrement(); + i_santaToken.burn(msg.sender); + _mintAndIncrementToUser(presentReceiver); } ``` By applying this recommendation, there is no need to worry about the approvals and the vulnerability - 'tokens can be burnt even though users don't approve' will have zero impact as the tokens are now burnt from the caller. Therefore, an attacker can't burn others token.

Support

FAQs

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

Give us feedback!