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
Lacks check to ensure the arbitrum sequencer is down
Summary
the functions getPrice() and getOriginalPrice() are vulnerable to the Arbitrum sequencer being down. The reason for this is that the functions do not check whether the sequencer is online before retrieving the price feed. If the sequencer is down, the functions will return outdated or stale price data, which could lead to errors in the smart contract
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
jprod15
medium
Lacks check to ensure the arbitrum sequencer is down
Summary
the functions getPrice() and getOriginalPrice() are vulnerable to the Arbitrum sequencer being down. The reason for this is that the functions do not check whether the sequencer is online before retrieving the price feed. If the sequencer is down, the functions will return outdated or stale price data, which could lead to errors in the smart contract
Vulnerability Detail
Impact
when sequencer is down, stale price is used for oracle
Code Snippet
https://github.com/sherlock-audit/2023-06-dodo/blob/main/new-dodo-v3/contracts/DODOV3MM/periphery/D3Oracle.sol#L48-L67
Tool used
Manual Review
Recommendation
recommend to add checks to ensure the sequencer is not down.
https://docs.chain.link/data-feeds/l2-sequencer-feeds
Duplicate of #62
The text was updated successfully, but these errors were encountered: