In the FEED_HORSE
macro, the three lines below calculate the modulo 17 of the timestamp. The issue arises when the timestamp is a multiple of 17, resulting in the modulo operation producing 0. Consequently, the jump instruction is skipped, leading to a transaction revert. It's important to note that Solidity code does not inherently include this specific calculation.
The impact includes a denial of service with a probability of 1/17 (each time the timestamp is a multiple of 17). This behavior is non-conforming to Solidity code, causing confusion for users, developers, and auditors.
To address this issue, remove the three lines above and the label for the jump:
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.