ChainlinkAdapterOracle will return the wrong price for asset if underlying aggregator hits minAnswer
Chainlink aggregators have a built in circuit breaker if the price of an asset goes outside of a predetermined price band. The result is that if an asset experiences a huge drop in value (i.e. LUNA crash) the price of the oracle will continue to return the minPrice instead of the actual price of the asset. This would allow user to continue borrowing with the asset but at the wrong price. This is exactly what happened to Venus on BSC when LUNA imploded.\\nChainlinkAdapterOracle uses the ChainlinkFeedRegistry to obtain the price of the requested tokens.\\n```\\nfunction latestRoundData(\\n  address base,\\n  address quote\\n)\\n  external\\n  view\\n  override\\n  checkPairAccess()\\n  returns (\\n    uint80 roundId,\\n    int256 answer,\\n    uint256 startedAt,\\n    uint256 updatedAt,\\n    uint80 answeredInRound\\n  )\\n{\\n  uint16 currentPhaseId = s_currentPhaseId[base][quote];\\n  //@audit this pulls the Aggregator for the requested pair\\n  AggregatorV2V3Interface aggregator = _getFeed(base, quote);\\n  require(address(aggregator) != address(0), "Feed not found");\\n  (\\n    roundId,\\n    answer,\\n    startedAt,\\n    updatedAt,\\n    answeredInRound\\n  ) = aggregator.latestRoundData();\\n  return _addPhaseIds(roundId, answer, startedAt, updatedAt, answeredInRound, currentPhaseId);\\n}\\n```\\n\\nChainlinkFeedRegistry#latestRoundData pulls the associated aggregator and requests round data from it. ChainlinkAggregators have minPrice and maxPrice circuit breakers built into them. This means that if the price of the asset drops below the minPrice, the protocol will continue to value the token at minPrice instead of it's actual value. This will allow users to take out huge amounts of bad debt and bankrupt the protocol.\\nExample: TokenA has a minPrice of $1. The price of TokenA drops to $0.10. The aggregator still returns $1 allowing the user to borrow against TokenA as if it is $1 which is 10x it's actual value.\\nNote: Chainlink oracles are used a just one piece of the OracleAggregator system and it is assumed that using a combination of other oracles, a scenario like this can be avoided. However this is not the case because the other oracles also have their flaws that can still allow this to be exploited. As an example if the chainlink oracle is being used with a UniswapV3Oracle which uses a long TWAP then this will be exploitable when the TWAP is near the minPrice on the way down. In a scenario like that it wouldn't matter what the third oracle was because it would be bypassed with the two matching oracles prices. If secondary oracles like Band are used a malicious user could DDOS relayers to prevent update pricing. Once the price becomes stale the chainlink oracle would be the only oracle left and it's price would be used.
Issue ChainlinkAdapterOracle will return the wrong price for asset if underlying aggregator hits minAnswer\\nChainlinkAdapterOracle should check the returned answer against the minPrice/maxPrice and revert if the answer is outside of the bounds:\\n```\\n    (, int256 answer, , uint256 updatedAt, ) = registry.latestRoundData(\\n        token,\\n        USD\\n    );\\n    \\n+   if (answer >= maxPrice or answer <= minPrice) revert();\\n```\\n
In the event that an asset crashes (i.e. LUNA) the protocol can be manipulated to give out loans at an inflated price
```\\nfunction latestRoundData(\\n  address base,\\n  address quote\\n)\\n  external\\n  view\\n  override\\n  checkPairAccess()\\n  returns (\\n    uint80 roundId,\\n    int256 answer,\\n    uint256 startedAt,\\n    uint256 updatedAt,\\n    uint80 answeredInRound\\n  )\\n{\\n  uint16 currentPhaseId = s_currentPhaseId[base][quote];\\n  //@audit this pulls the Aggregator for the requested pair\\n  AggregatorV2V3Interface aggregator = _getFeed(base, quote);\\n  require(address(aggregator) != address(0), "Feed not found");\\n  (\\n    roundId,\\n    answer,\\n    startedAt,\\n    updatedAt,\\n    answeredInRound\\n  ) = aggregator.latestRoundData();\\n  return _addPhaseIds(roundId, answer, startedAt, updatedAt, answeredInRound, currentPhaseId);\\n}\\n```\\n