Scroll Patches Proof Validator Vulnerability, Confirms No Exploitation

iconChainthink
Share
AI summary iconSummary
Scroll addressed a proof validator vulnerability in its batch version 10, confirming no exploitation occurred. This on-chain update follows the report of the issue on November 3 and its patch by November 10. The flaw could have allowed old proofs to validate arbitrary state and withdrawal roots. Scroll noted that forced batch mode was never activated, and all 748 final confirmations used standard proofs. Previous validator versions remain unaffected.

ChainThink reports that on November 11, according to an official announcement, Scroll has registered the repaired proof verifier for batch version 10 and confirmed that the vulnerability in the bundle proof verifier deployed on Ethereum mainnet was not exploited.

The vulnerability was reported on November 3 and patched on November 10. It was reported that the vulnerability could allow old valid proofs to be used with new public inputs, ultimately enabling the confirmation of arbitrary state roots and withdrawal roots.

Exploiting this vulnerability requires either a licensed prover role or entry into forced batch mode after seven consecutive days without finalization.

Scroll stated that the forced mode was never enabled, and all 748 final confirmations during the vulnerability period used standard proofs; validators from previous versions were unaffected.

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.