Users participate in the raffle; winners receive their entitled prizes, and the prize amounts will not be miscalculated.
When the value of fee exceeds type(uint64).max, using uint64(fee) will truncate the higher bits, causing the fee to decrease, resulting in a loss.
type(uint64).max can represent up to 18.5 ETH; if entranceFee == 1 ETH, then with roughly 93 participants the fee will begin to decrease.
Likelihood:
After calculation, when entranceFee is set to 1 ETH, only 93 participants are needed for uint64(fee) to be truncated and its value reduced. Therefore, the larger the entranceFee is set, the fewer participants are required for uint64(fee) to overflow, causing a loss of funds.
Impact:
The totalFees amount decreases, the funds will be permanently locked in the contract.
address(this).balance and uint256(totalFees) are unlikely to be equal
entranceFeeequal 1e18.
Initialize 100 players.
selectWinner()
Compare Expected Total Fees and Actual Total Fees.
withdrawFees()
expectRevert
Change the type of totalFees to uint256
uint64(fee) => fee
## 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.