You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 31, 2023. It is now read-only.
sherlock-admin opened this issue
Jul 1, 2023
· 0 comments
Labels
DuplicateA valid issue that is a duplicate of an issue with `Has Duplicates` labelMediumA valid Medium severity issueRewardA payout will be made for this issue
Oracle doesn't check if Arbitrum Sequencer is active
Summary
DODO V3 is going to deployed on mainnet, arbitrum, optimism, bnb chain, polygon, so when using Chainlink in L2 chains such as Arbitrum requires to check if the sequencer is down.
The bug could be leveraged by malicious actors to take advantage of the sequencer downtime.
Vulnerability Detail
There is a lack of a check if the L2 Arbitrum sequencer is down.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
DuplicateA valid issue that is a duplicate of an issue with `Has Duplicates` labelMediumA valid Medium severity issueRewardA payout will be made for this issue
skyge
medium
Oracle doesn't check if Arbitrum Sequencer is active
Summary
DODO V3 is going to deployed on
mainnet, arbitrum, optimism, bnb chain, polygon
, so when using Chainlink in L2 chains such as Arbitrum requires to check if the sequencer is down.The bug could be leveraged by malicious actors to take advantage of the sequencer downtime.
Vulnerability Detail
There is a lack of a check if the L2 Arbitrum sequencer is down.
Impact
could potentially be exploited by malicious actors to gain an unfair advantage.
Code Snippet
Links to same issue in past Sherlock contests being validated as a Medium:
Tool used
Manual Review
Recommendation
It is recommended to follow the code example of Chainlink:
https://docs.chain.link/data-feeds/l2-sequencer-feeds#example-code
Duplicate of #62
The text was updated successfully, but these errors were encountered: