Relying on block.timestamp for setting a swap deadline
Summary
The L2TokenReceiver.sol contract implements the deadline of the swap and increaseLiquidityCurrentRange wrong.
Vulnerability Details
Proposers can anticipate proposing single or consecutive blocks in advance. In this situation, a malicious validator can delay the transaction, strategically executing it at a more advantageous block number.
Impact
This provides no safeguard, as the block.timestamp will reflect the value of the block in which the transaction is included. Consequently, malicious validators can indefinitely withhold the transaction.
Tools Used
Manual review.
Recommendations
Consider enabling users to specify a deadline parameter for their transactions
Lead Judging Commences
Protocol should not use block.timestamp as deadline in Uniswap interactions because it renders the protection mechanism useless
Prize pool breakdown
Live
The contest is live. Earn rewards by submitting a finding.
Appeals
This is your time to appeal against judgements on your submissions.
Appeals Review
Appeals are being carefully reviewed by our judges.