Security readout for executives and security teams
Plain-English summary
This issue can make OpenZeppelin Cairo account contracts from version 0.2.0 unusable on StarkNet Goerli. The impact is availability, not data theft or transaction manipulation. Sources say the bug is fixed in v0.2.1 and was not seen in StarkNet’s testing framework.
Executive priority
Treat as a moderate availability issue. Prioritize teams relying on StarkNet Goerli accounts for development, testing, demos, or customer-facing testnet workflows. Main business urgency is avoiding blocked transactions and stalled delivery pipelines.
Technical view
CVE-2022-31153 affects OpenZeppelin cairo-contracts 0.2.0 account contracts, including vanilla and ethereum flavors. The vulnerable behavior prevents affected accounts from processing transactions on live Goerli deployments. CVSS 3.1 is 6.5 with high availability impact and no confidentiality or integrity impact.
Likely exposure
Exposure appears limited to projects that deployed OpenZeppelin Contracts for Cairo account contracts using v0.2.0 on StarkNet Goerli. The source bundle says only Goerli deployments of v0.2.0 accounts are affected.
Exploitation context
No active exploitation is cited, and the CVE is not listed as KEV in the supplied bundle. The main risk is operational disruption: affected accounts may be unable to process transactions on the affected live network.
Researcher notes
Evidence is specific to OpenZeppelin cairo-contracts v0.2.0 account contracts on Goerli. Do not generalize this to all StarkNet contracts or later OpenZeppelin releases. The advisory states the issue was patched in v0.2.1.
Mitigation direction
- Upgrade OpenZeppelin cairo-contracts from v0.2.0 to v0.2.1 or later.
- Identify and replace affected Goerli account deployments built from v0.2.0.
- Review OpenZeppelin advisory and v0.2.1 release notes before redeployment.
- Document any impacted testnet accounts and dependency changes.
Validation and detection
- Inventory Cairo dependencies for exact OpenZeppelin cairo-contracts v0.2.0 usage.
- Identify deployed StarkNet Goerli account contracts using the affected release.
- Confirm patched code or dependency lockfiles reference v0.2.1 or later.
- Check whether account transaction processing is restored after migration.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-664: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-31153 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H2.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/OpenZeppelin/cairo-contracts/security/advisories/GHSA-8mjr-jr5h-q2xrCVE reference · x_refsource_CONFIRM
- https://github.com/OpenZeppelin/cairo-contracts/issues/386CVE reference · x_refsource_MISC
- https://github.com/OpenZeppelin/cairo-contracts/pull/387CVE reference · x_refsource_MISC
- https://github.com/OpenZeppelin/cairo-contracts/commit/2cd60279c3332285d47edf9ee3888b71257acdc9CVE reference · x_refsource_MISC
- https://github.com/OpenZeppelin/cairo-contracts/blob/release-0.2.0/src/openzeppelin/account/library.cairo#L203CVE reference · x_refsource_MISC
- https://github.com/OpenZeppelin/cairo-contracts/releases/tag/v0.2.1CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of a Resource Through its Lifetime
Improper Control of a Resource Through its Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.