Cyber Resilience

CVE-2023-30629

Vyperlang Vyper 0.3.1 – 0.3.8

Public PoC
Published
24 April 2023
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS Score 0.0088 56th percentile
Risk Priority 59 floored blend · peak EPSS

Summary

CVE-2023-30629 is a high-severity Always-Incorrect Control Flow Implementation (CWE-670) vulnerability in Vyperlang Vyper. Its CVSS base score is 7.5 (High).

Operationally, ranked in the top 44% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

EU & UK References

Vulnerability Data

Vyper is a Pythonic Smart Contract Language for the ethereum virtual machine. In versions 0.3.1 through 0.3.7, the Vyper compiler generates the wrong bytecode. Any contract that uses the `raw_call` with `revert_on_failure=False` and `max_outsize=0` receives the wrong response from `raw_call`.…

more

Depending on the memory garbage, the result can be either `True` or `False`. A patch is available and, as of time of publication, anticipated to be part of Vyper 0.3.8. As a workaround, one may always put `max_outsize>0`.

CWE(s)
CWE-670

Related Threats

CVEs Like This One

CVE-2025-21607Same product: Vyperlang Vyper
CVE-2023-41052Same product: Vyperlang Vyper
CVE-2023-40015Same product: Vyperlang Vyper
CVE-2023-32675Same product: Vyperlang Vyper
CVE-2023-37902Same product: Vyperlang Vyper
CVE-2023-39363Same product: Vyperlang Vyper
CVE-2024-24561Same product: Vyperlang Vyper
CVE-2023-42441Same product: Vyperlang Vyper
CVE-2024-32646Same product: Vyperlang Vyper
CVE-2023-42443Same product: Vyperlang Vyper

Affected Assets

vyperlang
vyper
0.3.1 — 0.3.8

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V9.2.1

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent incorrect control-flow implementations via reviews, testing, and static analysis.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance can detect paths that deviate from intended logic.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle processes can catch incorrect control-flow logic during design and code review.

A.8.28 Secure coding partial match
prevents

Secure coding standards and reviews directly target flawed control-flow implementations.

A.8.32 Change management partial match
prevents

Change-management gates may prevent deployment of flawed logic but do not address the coding defect itself.

References