Skip to content

OpenZeppelin Contracts's Cross chain utilities for Arbitrum L2 see EOA calls as cross chain calls

Moderate severity GitHub Reviewed Published Jul 28, 2022 in OpenZeppelin/openzeppelin-contracts • Updated Feb 2, 2023

Package

npm @openzeppelin/contracts (npm)

Affected versions

>= 4.6.0, < 4.7.2

Patched versions

4.7.2
npm @openzeppelin/contracts-upgradeable (npm)
>= 4.6.0, < 4.7.2
4.7.2

Description

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

OpenZeppelin/openzeppelin-contracts#3578

For more information

If you have any questions or comments about this advisory, or need assistance deploying a fix, email us at security@openzeppelin.com.

References

@frangio frangio published to OpenZeppelin/openzeppelin-contracts Jul 28, 2022
Published by the National Vulnerability Database Aug 1, 2022
Published to the GitHub Advisory Database Aug 14, 2022
Reviewed Aug 14, 2022
Last updated Feb 2, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

EPSS score

0.061%
(28th percentile)

Weaknesses

CVE ID

CVE-2022-35916

GHSA ID

GHSA-9j3m-g383-29qr

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.