Chainlink's latestRoundData might return stale or incorrect results
The staleCheckLatestRoundData() function in the OracleLib.sol fetches the asset price from a Chainlink aggregator V3 using the latestRoundData function as used at L-27.
However, there are no checks on roundID, resulting in stale prices. The oracle wrapper calls out to a chainlink oracle receiving the latestRoundData().
Stale prices could put funds at risk. According to Chainlink's documentation, This function does not error if no answer has been reached but returns 0, causing an incorrect price fed to the PriceOracle. The external Chainlink oracle, which provides index price information to the system, introduces risk inherent to any dependency on third-party data sources. For example, the oracle could fall behind or otherwise fail to be maintained, resulting in outdated data being fed to the index price calculations. Oracle reliance has historically resulted in crippled on-chain systems, and complications that lead to these outcomes can arise from things as simple as network congestion.
Chainlink reference-
https://docs.chain.link/data-feeds/historical-data#getrounddata-return-values
Manual Review
Consider adding missing checks for stale data.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.