The scoreBoard::setPrediction
function contains a mathematical expression with an incorrect order of operations, leading to unintended time calculations that could affect the function's behavior.
In the setPrediction
function, there's the following time check:
However, the intended calculation should subtract 18000 before multiplying by the match number:
lets say matchnumber = 1
Impact
This vulnerability could lead to incorrect time calculations, potentially allowing predictions to be set at unintended times. Depending on the value of matchNumber
, the time window for setting predictions could be significantly different from what was intended, compromising the fairness and integrity of the prediction system.
This ensures that one interval is subtracted before multiplying by the match number.
In both contracts there is a similar error in the computation of the timestamps of the matches.
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.