The withdrawFees() function should allow the protocol owner to withdraw accumulated fees. The function should work reliably regardless of external actions.
The function requires address(this).balance == totalFees, but ETH can be forcibly sent to any contract via selfdestruct. This permanently breaks the equality check.
Likelihood: High
Any attacker can force ETH into the contract using selfdestruct
The attack costs only the small amount of ETH sent plus gas
Impact: Medium
All accumulated fees become permanently locked
Protocol loses all past and future revenue
No recovery mechanism exists
PuppyRaffle contract has collected 1 ETH in fees (totalFees = 1 ETH)
Attacker deploys a contract: contract Kill { constructor(address t) payable { selfdestruct(payable(t)); } }
Attacker deploys with 0.01 ETH targeting PuppyRaffle
0.01 ETH is forcibly sent to PuppyRaffle without triggering any functions
address(this).balance is now 1.01 ETH
withdrawFees() always reverts: 1.01 ETH != 1 ETH
All current and future fees are permanently locked
## 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"); } ```
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.