CVE-2020-37286 json
Vyper 0.1.0b4 before 0.3.0 Memory Corruption via Nested Internal Function Calls
published last mo. modified 13d ago also EUVD-2020-31282 , GHSA-2r3x-4mrv-mcxf
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 21%
- public exploits
- 0
- none known
Summary
Vyper from 0.1.0b4 before 0.3.0 contains a memory corruption vulnerability caused by an incorrect stack tip pointer when internal function calls appear inside tuples or nested calls. Contracts using such calls as tuple elements, call arguments, or builtin arguments like concat or ecrecover can return corrupted values or pass wrong arguments to external calls.
Patch / fix
- pypi vyper 0.2.6
- vyperlang vyper 0.3.0
- github.com/vyperlang/vyper@74ba67d commit
- github.com/vyperlang/vyper#2186 pull request
- github.com/vyperlang/vyper/releases/tag/v0.2.6 release
Is CVE-2020-37286 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 FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2020-37286 updated cvss 6.5
vyper: vyper: Memory corruption via nested internal function calls
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 13d ago
Exploit prediction
0.28% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.3 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N |
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L |
| CNA | 4.0 | 8.3 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | vyper | <0.2.6 |
0.2.6 |
Affected products
- vyperlang vyper
Classification
References
-
github.com
/vyperlang/vyper/pull/2186
web
-
github.com
/vyperlang/vyper/commit/74ba67d4bec5f8be4f05759e37d2bfb1463e0441
web
-
github.com
/vyperlang/vyper/security/advisories/GHSA-2r3x-4mrv-mcxf
vendor-advisory, web
-
vulncheck.com
/advisories/vyper-0.1-0b4-before-0.3.0-memory-corruption-via-nested-internal-function-calls
third-party-advisory
-
github.com
/vyperlang/vyper
package
-
github.com
/vyperlang/vyper/releases/tag/v0.2.6
web
Sources
- CVE List CVE-2020-37286
- GitHub Advisory GHSA-2r3x-4mrv-mcxf
- NVD CVE-2020-37286
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.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.