Headline
CVE-2022-35916: Fix arbitrum L1 to L2 crosschain call detection by Amxx · Pull Request #3578 · OpenZeppelin/openzeppelin-contracts
OpenZeppelin Contracts is a library for secure smart contract development. Contracts using the cross chain utilities for Arbitrum L2, CrossChainEnabledArbitrumL2 or LibArbitrumL2, will classify direct interactions of externally owned accounts (EOAs) as cross chain calls, even though they are not started on L1. This issue has been patched in v4.7.2. Users are advised to upgrade. There are no known workarounds for this issue.
Conversation
frangio previously approved these changes Jul 25, 2022
Amxx enabled auto-merge (squash)
Jul 25, 2022
Amxx deleted the fix/crosschain/arbitrum branch
Jul 25, 2022
frangio pushed a commit that referenced this issue
Jul 26, 2022
* Fix arbitrum L1 to L2 crosschain call detection
* fix BridgeArbitrumL2Mock
* update changelog
Co-authored-by: Francisco Giordano [email protected] (cherry picked from commit 81336ae)
Related news
### Impact Contracts using the cross chain utilies for Arbitrum L2, `CrossChainEnabledArbitrumL2` or `LibArbitrumL2`, will classify direct interactions of externally owned accounts (EOAs) as cross chain calls, even though they are not started on L1. This is assessed as low severity because any action taken by an EOA on the contract could also be taken by the EOA through the bridge if the issue was not present. ### Patches This issue has been patched in v4.7.2. ### References https://github.com/OpenZeppelin/openzeppelin-contracts/pull/3578 ### For more information If you have any questions or comments about this advisory, or need assistance deploying a fix, email us at [[email protected]](mailto:[email protected]).