https://github.com/code-423n4/2024-07-loopfi/blob/57871f64bdea450c1f04c9a53dc1a78223719164/src/CDPVault.sol#L52-L53
Now whenever any pricing logic is to be implemented, this function is called: 
However, the problem is that if anything happens to the underlying oracle then the Vault is completely bricked. For example, if the attached oracle is a Chainlink oracle that gets put down for maintenance or for change of address, the whole vaults logic that relies on pricing is broken.
QA, due to the very low likelihood. However, if this occurs, liquidations are completely broken allowing users to accrue bad debt, so is the modifyCollateralAndDebt() and every other function that relies on using the spot prices.
Since there is already a support of multiple price providers in protocol, consider modifying CDPVault#spotPrice() to first try to get the price from the current/primary oracle set, then set a secondary/fallback oracle for the collateral in case the first one fails, this can easily be achieved by a try/catch logic.
To mitigate the risk associated with relying solely on a primary oracle for pricing information in the CDPVault, implementing a fallback oracle mechanism is crucial. This approach ensures that if the primary oracle fails or undergoes maintenance, the system can still function by relying on a secondary oracle. This fallback mechanism can be implemented using Soliditys try/catch error handling mechanism introduced in Solidity version 0.6.x.
Heres how you can modify the spotPrice() function in the CDPVault.sol contract to incorporate a fallback oracle:
