Security readout for executives and security teams
Plain-English summary
CVE-2022-29255 is a Vyper compiler bug that could make some Ethereum smart contracts behave incorrectly. In affected versions, an external call with no return value could evaluate the target contract address twice, including any side effects. The issue affects Vyper versions before 0.3.4 and was fixed in 0.3.4.
Executive priority
Treat this as high priority for teams owning Vyper-based smart contracts, especially financial or governance contracts. It is not a broad infrastructure emergency from the provided evidence, but affected contracts can have business-critical integrity consequences and may be hard to remediate once deployed.
Technical view
Vyper <0.3.4 could duplicate evaluation of a contract address expression during an external call with no return value. If that expression had side effects, generated contract behavior could diverge from source-code intent, creating integrity risk and limited availability impact. The CVE maps to CWE-670 and has CVSS 3.1 score 8.2.
Likely exposure
Exposure is most likely in projects that compiled Ethereum contracts with Vyper versions before 0.3.4 and used no-return external calls where the address expression could have side effects. The provided sources do not identify specific deployed contracts, package manifests, or CPEs.
Exploitation context
The source bundle does not show CISA KEV listing or cite active exploitation. The practical risk depends on whether vulnerable compiled contracts exist and whether the duplicated address evaluation changes contract state, control flow, or value movement.
Researcher notes
The key research question is whether compiled artifacts came from Vyper <0.3.4 and include no-return external calls with side-effecting address evaluation. Sources confirm the flaw and fix version, but do not provide evidence of active exploitation or a list of affected deployed contracts.
Mitigation direction
- Upgrade Vyper build tooling to version 0.3.4 or later.
- Identify contracts compiled with Vyper versions before 0.3.4.
- Review vendor advisory and patch commit before changing production deployment workflows.
- For upgradeable contracts, assess recompilation and redeployment through established governance controls.
- For immutable deployments, document residual risk and monitor vendor or project-specific guidance.
Validation and detection
- Inventory Vyper compiler versions used in historical and current builds.
- Search code for external calls with no return value.
- Review target address expressions for state changes or other side effects.
- Confirm CI and release pipelines pin Vyper 0.3.4 or later.
- Map any affected deployed contracts to upgradeability and operational impact.
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-670: 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-29255 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
- High
- CVSS
- 8.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
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:N/UI:N/S:U/C:N/I:H/A:L3.94.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/vyperlang/vyper/security/advisories/GHSA-4v9q-cgpw-cf38CVE reference · x_refsource_CONFIRM
- https://github.com/vyperlang/vyper/commit/6b4d8ff185de071252feaa1c319712b2d6577f8dCVE 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.
Always-Incorrect Control Flow Implementation
Always-Incorrect Control Flow Implementation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.