No check for report in submitReportData

[avsetsin]

Two contracts have a similar problem: ValidatorExitBusOracle and AccountingOracle.

After the consensus phase of the report, the oracle daemon should deliver the data for which the consensus has been gathered by calling the submitReportData method. The method does not check if the data has been previously submitted, which might lead to repeated calls to this method by another or the same oracle daemon.

In the case of ValidatorExitBusOracle, this will lead to duplicate exit requests and incorrect accounting of the total number of requested validators to exit stored in TOTAL_REQUESTS_PROCESSED_POSITION.

In the case of AccountingOracle, in most cases such a scenario should lead to a transaction revert. However, if all operations performed in the report, such as withdrawal from Withdrawal and Execution Layer Rewards vaults, are possible to perform again, it can lead to a serious mismatch in the protocol state.

[TheDZhon]

The fix is integrated into the latest Lido 2.0 beta2 release.