CVE-2022-24788 json
Buffer overflow in Vyper
published 2022-04-13 4 y ago modified 2026-06-17 4 mo ago also GHSA-4mrx-6fxm-8jpg , PYSEC-2022-197 , EUVD-2022-0354
- cvss
- 7.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 62%
- public exploits
- 0
- none known
Summary
Vyper is a pythonic Smart Contract Language for the ethereum virtual machine. Versions of vyper prior to 0.3.2 suffer from a potential buffer overrun. Importing a function from a JSON interface which returns `bytes` generates bytecode which does not clamp bytes length, potentially resulting in a buffer overrun. Users are advised to upgrade. There are no known workarounds for this issue.
Patch / fix
- pypi vyper 0.3.2
- vyperlang vyper 0.3.2
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
0.99% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:N |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 7.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | vyper | <0.3.2 |
0.3.2 |
Affected products
- vyperlang vyper
Classification
References
-
github.com
/vyperlang/vyper/commit/049dbdc647b2ce838fae7c188e6bb09cf16e470b
web, patch, third-party-advisory
-
github.com
/vyperlang/vyper/security/advisories/GHSA-4mrx-6fxm-8jpg
web, patch, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-24788
advisory
-
github.com
/pypa/advisory-database/tree/main/vulns/vyper/PYSEC-2022-197.yaml
web
-
github.com
/vyperlang/vyper
package
Sources
- CVE List CVE-2022-24788
- GitHub Advisory GHSA-4mrx-6fxm-8jpg
- NVD CVE-2022-24788
- OSV PYSEC-2022-197
Fencer Vulns 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.