Description:
Typecast overflow occurs when a value is cast in a smaller data type.Due to which chances of Precision loss and overFlow as well . In line Line: 195 the typecast lead to trucate the value (precision) in PuppyRaffle::totalFees variable which can lead to the permanent lock of funds in the contract.
Impact:
When the value stored in PuppyRaffle::fee exceeds the maximum value of uint64, it will loose the Precision due to overflow and the value of PuppyRaffle::totalFees will be incorrect. This can lead to the permanent lock of funds in the contract as the contract will not be able to withdraw the fees correctly.
Proof of Concept:
when the value of fee is greater than uint64 max value which is 18446744073709551615, the value of PuppyRaffle::fee will be truncated to fit into uint64, resulting in a loss of precision.
Recommended Mitigation:
The Recommended Mitigation is to use a larger data type for PuppyRaffle::totalFees variable, such as uint256, to prevent overflow and ensure that all fees can be accurately tracked and withdrawn.
## 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.