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 Nov 26, 2023. It is now read-only.
sherlock-admin opened this issue
May 24, 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
latestRoundData could return stale or incorrect result
Summary
USSD uses Chainlink’s price feeds in the stable oracles. But it doesn't contain a check for round completeness which could result in stale or incorrect prices.
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
GimelSec
medium
latestRoundData
could return stale or incorrect resultSummary
USSD uses Chainlink’s price feeds in the stable oracles. But it doesn't contain a check for round completeness which could result in stale or incorrect prices.
Vulnerability Detail
USSD uses
priceFeed.latestRoundData()
without any check.https://github.com/sherlock-audit/2023-05-USSD/blob/main/ussd-contracts/contracts/oracles/StableOracleWETH.sol#L23
Impact
The stale and incorrect price could harm the protocol.
Code Snippet
https://github.com/sherlock-audit/2023-05-USSD/blob/main/ussd-contracts/contracts/oracles/StableOracleWETH.sol#L23
https://github.com/sherlock-audit/2023-05-USSD/blob/main/ussd-contracts/contracts/oracles/StableOracleWBTC.sol#L23
https://github.com/sherlock-audit/2023-05-USSD/blob/main/ussd-contracts/contracts/oracles/StableOracleDAI.sol#L48
Tool used
Manual Review
Recommendation
Add a check to prevent stale and incorrect prices.
Duplicate of #31
The text was updated successfully, but these errors were encountered: