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 5, 2023. It is now read-only.
sherlock-admin opened this issue
Apr 30, 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
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
cducrest-brainbot
medium
ChainlinkAdapterOracle can still give stale data
Summary
The implemented fix to issue sherlock-audit/2023-02-blueberry-judging#94 is not sufficient. The ChainlinkAdapterOracle can still give stale data.
Vulnerability Detail
The fix is the following:
function getPrice(address token_) external view override returns (uint256) { // remap token if possible address token = remappedTokens[token_]; if (token == address(0)) token = token_; uint256 maxDelayTime = timeGaps[token]; if (maxDelayTime == 0) revert Errors.NO_MAX_DELAY(token_); // Get token-USD price uint256 decimals = registry.decimals(token, USD); (, int256 answer, , uint256 updatedAt, ) = registry.latestRoundData( token, USD ); if (updatedAt < block.timestamp - maxDelayTime) revert Errors.PRICE_OUTDATED(token_); + if (answer <= 0) revert Errors.PRICE_NEGATIVE(token_); return (answer.toUint256() * Constants.PRICE_PRECISION) / 10 ** decimals; }
There is no check regarding
answeredInRound
androundId
, so the price data could be carried over.Impact
Correct price is detrimental to the protocol as a whole. It is required to guarantee proper borrow limits, liquidation conditions, etc ...
An incorrect price may result in loss of funds for users e.g. when they are liquidated due to an incorrect price while they should not have.
Code Snippet
https://github.com/sherlock-audit/2023-04-blueberry/blob/96eb1829571dc46e1a387985bd56989702c5e1dc/blueberry-core/contracts/oracle/ChainlinkAdapterOracle.sol#L77-L97
Tool used
Manual Review
Reference
code-423n4/2022-04-backd-findings#17
https://docs.chain.link/data-feeds/historical-data
Recommendation
Add
require(answeredInRound >= roundID, "Stale price");
as an additional check:Duplicate of #118
The text was updated successfully, but these errors were encountered: