The ChainlinkOracle contract's _getData() implementation exposes critical vulnerabilities in QuantAMM's Temporal Function Market Making (TFMM) mechanism by lacking price deviation validation between consecutive oracle updates. Within QuantAMM's automated portfolio management framework, this vulnerability becomes particularly severe as the TFMM system continuously adjusts weights based on oracle price inputs.
The absence of deviation checks creates a dangerous scenario where QuantAMM's weight adjustment algorithm could execute extreme rebalancing operations based on manipulated or erroneous prices. This vulnerability is amplified by the protocol's composite pool architecture, where a single compromised price feed could trigger cascading rebalancing events across multiple interconnected strategies.
During periods of market volatility, the TFMM mechanism's reliance on continuous price updates becomes a critical point of failure. Flash crashes or price spikes could cause the protocol to execute rapid, unwarranted portfolio reallocations, potentially destabilizing entire strategy implementations. The risk is compounded in QuantAMM's BTF structure, where automated trading strategies could interpret manipulated price movements as legitimate trading signals, leading to systematic portfolio mismanagement.
Implement price deviation validation with configurable thresholds:
LightChaser: ## [Low-25] Chainlink answer is not compared against min/max values
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.