The totalFees variable tracks accumulated protocol fees and should accurately reflect all fees collected across raffles.
The fee is calculated as uint256 but totalFees is declared as uint64. The unsafe cast uint64(fee) silently truncates values exceeding ~18.4 ETH, causing significant fee loss.
Likelihood: Medium
Occurs when a raffle collects significant participation (>92 ETH total, >18.4 ETH in fees)
Popular raffles with high entrance fees easily exceed this threshold
Impact: High
Protocol loses track of actual fees collected
Significant revenue loss for the protocol owner
A popular raffle attracts many participants
Total entrance fees collected result in a fee value of 20 ETH
uint64 max is approximately 18.4 ETH
uint64(20 ETH) overflows and wraps to approximately 1.6 ETH
totalFees records 1.6 ETH instead of 20 ETH
Protocol loses 18.4 ETH in untracked fees
## Description ## Vulnerability Details The type conversion from uint256 to uint64 in the expression 'totalFees = totalFees + uint64(fee)' may potentially cause overflow problems if the 'fee' exceeds the maximum value that a uint64 can accommodate (2^64 - 1). ```javascript totalFees = totalFees + uint64(fee); ``` ## POC <details> <summary>Code</summary> ```javascript function testOverflow() public { uint256 initialBalance = address(puppyRaffle).balance; // This value is greater than the maximum value a uint64 can hold uint256 fee = 2**64; // Send ether to the contract (bool success, ) = address(puppyRaffle).call{value: fee}(""); assertTrue(success); uint256 finalBalance = address(puppyRaffle).balance; // Check if the contract's balance increased by the expected amount assertEq(finalBalance, initialBalance + fee); } ``` </details> In this test, assertTrue(success) checks if the ether was successfully sent to the contract, and assertEq(finalBalance, initialBalance + fee) checks if the contract's balance increased by the expected amount. If the balance didn't increase as expected, it could indicate an overflow. ## Impact This could consequently lead to inaccuracies in the computation of 'totalFees'. ## Recommendations To resolve this issue, you should change the data type of `totalFees` from `uint64` to `uint256`. This will prevent any potential overflow issues, as `uint256` can accommodate much larger numbers than `uint64`. Here's how you can do it: Change the declaration of `totalFees` from: ```javascript uint64 public totalFees = 0; ``` to: ```jasvascript uint256 public totalFees = 0; ``` And update the line where `totalFees` is updated from: ```diff - totalFees = totalFees + uint64(fee); + totalFees = totalFees + fee; ``` This way, you ensure that the data types are consistent and can handle the range of values that your contract may encounter.
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.