The setQueueDepositParams function in the PriorityPool contract lacks a check to ensure that the minimum deposit value is less than or equal to the maximum deposit value. This oversight could potentially lead to logical errors in the contract's operation.
In the PriorityPool.sol contract, the setQueueDepositParams function allows the owner to set the minimum and maximum deposit parameters without validating their relationship:
This function lacks a check to ensure that _queueDepositMin is less than or equal to _queueDepositMax. Without this validation, it's possible to set these parameters in a way that could cause logical errors in other parts of the contract that rely on these values.
The impact of this vulnerability is low because:
The function is restricted to the contract owner, limiting the potential for malicious exploitation.
It doesn't directly affect user funds or cause immediate security risks.
However, if the parameters are set incorrectly, it could lead to unexpected reverts in functions that rely on these parameters, such as _depositQueuedTokens.
Manual review
To address this vulnerability, it's recommended to add a simple check in the setQueueDepositParams function:
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.