CVE-2023-30629 json
Vyper's raw_call with outsize=0 and revert_on_failure=False returns incorrect success value
published 3y ago modified 2mo ago also GHSA-w9g2-3w7p-72g9 , PYSEC-2023-131 , EUVD-2023-0263
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 59%
- public exploits
- 0
- none known
Summary
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`. 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`.
Patch / fix
- pypi vyper 0.3.8
- vyperlang vyper 0.3.8
- github.com/vyperlang/vyper@851f7a1 commit
- github.com/lidofinance/gate-seals#5 pull request
Is CVE-2023-30629 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.88% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-15).
Exploits and checks
- github.com https://github.com/vyperlang/vyper/security/advisories/GHSA-w9g2-3w7p-72g9 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | vyper | >=0.3.1, <0.3.8 |
0.3.8 |
Affected products
- vyperlang vyper
Classification
- Weakness
-
- CWE-670 Always-Incorrect Control Flow Implementation
References
-
github.com
/lidofinance/gate-seals/pull/5/files
web, patch
-
github.com
/vyperlang/vyper/commit/851f7a1b3aa2a36fd041e3d0ed38f9355a58c8ae
web, patch
-
github.com
/vyperlang/vyper/security/advisories/GHSA-w9g2-3w7p-72g9
web, exploit, vendor-advisory, advisory
-
docs.vyperlang.org
/en/v0.3.7/built-in-functions.html#raw_call
web, product
-
github.com
/lidofinance/gate-seals/blob/051593e74df01a4131c485b4fda52e691cd4b7d8/contracts/GateSeal.vy#L164
web, product
-
nvd.nist.gov
/vuln/detail/CVE-2023-30629
advisory
-
github.com
/pypa/advisory-database/tree/main/vulns/vyper/PYSEC-2023-131.yaml
web
-
github.com
/vyperlang/vyper
package
Sources
- CVE List CVE-2023-30629
- GitHub Advisory GHSA-w9g2-3w7p-72g9
- NVD CVE-2023-30629
- OSV PYSEC-2023-131
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.