The setBoostParameters function in the BoostController contract allows the maxBoost parameter to be set up to 50000, while the MAX_BOOST constant is defined as 25000. This inconsistency creates a discrepancy between the contract's constant value and the allowed range for maxBoost, potentially leading to confusion, unintended behavior, or vulnerabilities in the boost calculation logic.
MAX_BOOST is defined as 25000 in the BoostController contract
However, the setBoostParameters function allows the maxBoost parameter to be set up to 50000
The MAX_BOOST constant suggests that the maximum boost multiplier is 2.5x, but setBoostParameters allows it to be set up to 5x. This inconsistency can lead to confusion for developers and users.
If maxBoost is set to a value higher than MAX_BOOST, it may conflict with other parts of the contract that rely on the MAX_BOOST constant.
The impact is Low, the likelihood is High, so the severity is Low.
Manual Review
To resolve this inconsistency, the setBoostParameters function should enforce the same maximum value as the MAX_BOOST constant. Here is the updated code:
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.