The BoostController::setBoostParameters
function lacks proper validation for the minBoost
parameter. While it checks that maxBoost
is greater than minBoost
and that maxBoost
does not exceed a hard limit, it does not validate that minBoost is within a reasonable range. This could allow minBoost
to be set to an invalid or unintended value, potentially disrupting the protocol's boost calculation logic
In the BoostController::setBoostParameters
function:
The vulnerability lies in the following part of the setBoostParameters function:
While the function ensures that maxBoost
is greater than minBoost
and that maxBoost
does not exceed 50000
, it does not validate the lower bound of minBoost
.
For example:
If minBoost
is set to 0
, it could lead to unintended behaviour in boost calculations.
If minBoost
is set to an excessively low value, it could disrupt the protocol's economic model or lead to unfair advantages for users.
An invalid minBoost value could disrupt the boost calculation logic
Manual code review
To mitigate this vulnerability, add input validation for minBoost to ensure it is within a reasonable range
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.