A cached validity flag serves expired or invalid prices as if they were current
- Severity
- High
- Class
- Oracle integrity
- System
- On-chain price oracle
Consumers read a price the oracle should have marked invalid, acting on stale or voided data in production.
An oracle cached whether its latest price was valid, but the cached flag outlived the conditions that justified it. Prices that had expired, been voided, or failed their quorum could still be served as valid because the cache still said so.
Anything reading that oracle inherits the lie, and price feeds are exactly where a stale read turns into a bad liquidation or an underpriced trade.
Why it rated High
Stale-price reads by a production consumer, with real financial consequences downstream, short of a direct drain by the reporter.
The fix class
Re-evaluate validity at read time rather than trusting a cached flag that can go stale.
