CVE-2018-18920 json
Py-EVM is vulnerable to arbitrary bytecode injection
published 7y ago modified 4mo ago also GHSA-vqgp-4jgj-5j64 , PYSEC-2018-155 , PYSEC-2018-96 , EUVD-2018-0118
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.9%
- EPSS 2.9% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known
Summary
Py-EVM v0.2.0-alpha.33 allows attackers to make a vm.execute_bytecode call that triggers computation._stack.values with '"stack": [100, 100, 0]' where b'\x' was expected, resulting in an execution failure because of an invalid opcode. This is reportedly related to "smart contracts can be executed indefinitely without gas being paid."
Patch / fix
- pypi py-evm 0.2.0a33
Is CVE-2018-18920 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 FencerExploit prediction
2.93% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/ethereum/py-evm/issues/1448 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
| GitHub | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| OSV | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | py-evm | <=0.2.0a33 <0.2.0a33 |
0.2.0a33 |
| pypi | evm-py | <=0.2.0-alpha\.33 |
no fix listed |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
github.com
/ethereum/py-evm/issues/1448
web, exploit, third-party-advisory, report, evidence
-
twitter.com
/AlexanderFisher/status/1060923428641878019
web, third-party-advisory, advisory
-
twitter.com
/NettaLab/status/1060889400102383617
web, third-party-advisory, advisory
-
reddit.com
/r/ethereum/comments/9vkk2g/netta_labs_claim_to_have_found_a_vulnerability_in/e9d3wyx/
third-party-advisory, web, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2018-18920
advisory
-
github.com
/advisories/GHSA-vqgp-4jgj-5j64
advisory
-
github.com
/ethereum/py-evm
package
-
github.com
/pypa/advisory-database/tree/main/vulns/evm-py/PYSEC-2018-155.yaml
web
-
github.com
/pypa/advisory-database/tree/main/vulns/py-evm/PYSEC-2018-96.yaml
web
-
reddit.com
/r/ethereum/comments/9vkk2g/netta_labs_claim_to_have_found_a_vulnerability_in/e9d3wyx
web
Sources
- CVE List CVE-2018-18920
- GitHub Advisory GHSA-vqgp-4jgj-5j64
- NVD CVE-2018-18920
- OSV PYSEC-2018-96
- OSV PYSEC-2018-155
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.