Contract: LSTRewardsSplitter.sol
Line: 151
The updateFee() function in the LSTRewardsSplitter contract lacks proper input validation, potentially leading to security vulnerabilities and unexpected behavior.
The function does not validate that the _receiver address is non-zero, potentially allowing fees to be sent to the zero address.
The _index validation allows updating the fee at index 0, which may not be intended behavior.
There's no upper limit check on the _feeBasisPoints parameter, potentially allowing unreasonably high fees to be set for individual receivers.
Original Code:
These issues could lead to:
Loss of funds if fees are accidentally set to the zero address
Unintended modification of a potentially protected fee at index 0
Manipulation of fee structures that could drain rewards disproportionately
Remix IDE Desktop
Proposed Code Change with reduced SLOC:
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.