Summary

The missing L2 Sequencer bug in the OracleLib.sol contract can cause the contract to fail to provide accurate or up-to-date data. This can have a number of implications, including inaccurate or outdated data, loss of funds, and denial of service.

Vulnerability Details

There is no sequencer up-time check which can lead to stale price

Impact

The missing L2 Sequencer bug can have a significant impact on users of the OracleLib.sol contract. If the contract is using stale data, the results it provides may be inaccurate or outdated. This can lead to problems for users of the contract, such as making bad financial decisions or losing money. Additionally, if the contract fails to execute transactions properly, users may lose funds. Finally, if the contract is unavailable, users may not be able to use it. This can be a problem for users who rely on the contract for important services.

Tools Used

Manual Review

Recommendations

Add a check to the OracleLib contract to ensure that the L2 sequencer is available before calling the getPrice function.