Skip to content

OpenZeppelin Contracts for Cairo account cannot process transactions on Goerli

Moderate severity GitHub Reviewed Published Jul 14, 2022 in OpenZeppelin/cairo-contracts • Updated Jan 27, 2023

Package

pip openzeppelin-cairo-contracts (pip)

Affected versions

< 0.2.1

Patched versions

0.2.1

Description

Impact

This vulnerability affects all accounts (vanilla and ethereum flavors) in the v0.2.0 release of OpenZeppelin Contracts for Cairo, which are not whitelisted on StarkNet mainnet, so only goerli deployments of v0.2.0 accounts are affected.

This faulty behavior is not observed in StarkNet's testing framework, so don't rely on it passing to detect this issue on custom accounts.

Patches

This bug has been patched in v0.2.1.

References

The issue is detailed in OpenZeppelin/cairo-contracts#386.

For more information

If you have any questions or comments about this advisory:

References

@martriay martriay published to OpenZeppelin/cairo-contracts Jul 14, 2022
Published by the National Vulnerability Database Jul 15, 2022
Published to the GitHub Advisory Database Jul 15, 2022
Reviewed Jul 15, 2022
Last updated Jan 27, 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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:L/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.347%
(72nd percentile)

Weaknesses

CVE ID

CVE-2022-31153

GHSA ID

GHSA-8mjr-jr5h-q2xr

Source code

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