This arises from a lack of validation on score inputs, allowing validators to submit any value, including extreme ones, to manipulate task results
Protocol does not validate the score values inputted by the validators, to check that it falls within the acceptable range:
As we can see, the scores do not get checked, to ensure they are in the acceptable range.
This allows validators to enter any uint256 value as the score, encouraging malicious validators to input absurdly high values, like 2^256-1 to significantly skew and manipulate the score values.
This allows validators to input arbitrary values for scores without range validation, which can be exploited to manipulate task outcomes. Malicious validators could enter extreme values, like 2^{256} - 1 , to artificially skew the scores and distort the task’s result, potentially favoring certain outcomes
Manual Review
If score > 1e18, revert
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.