ghsa-pvh2-pj76-4m96
Vulnerability from github
Impact
In evm
crate < 0.31.0
, JUMPI
opcode's condition is checked after the destination validity check. However, according to Geth and OpenEthereum, the condition check should happen before the destination validity check.
Patches
This is a high severity security advisory if you use evm
crate for Ethereum mainnet. In this case, you should update your library dependency immediately to on or after 0.31.0
.
This is a low severity security advisory if you use evm
crate in Frontier or in a standalone blockchain, because there's no security exploit possible with this advisory. It is not recommended to update to on or after 0.31.0
until all the normal chain upgrade preparations have been done. If you use Frontier or other pallet-evm
based Substrate blockchain, please ensure to update your spec_version
before updating this. For other blockchains, please make sure to follow a hard-fork process before you update this.
Workarounds
If you are dependent on an older version of evm
and cannot update due to API interface changes, please contact Wei by email (wei@that.world), who will be happy to help you to publish patch releases for older evm
versions.
References
Fix PR: https://github.com/rust-blockchain/evm/pull/67
For more information
If you have any questions or comments about this advisory:
* Open an issue in the evm
repo.
Special thanks
Special thanks to @rakita for reporting this issue.
{ "affected": [ { "package": { "ecosystem": "crates.io", "name": "evm" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "0.31.0" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2021-41153" ], "database_specific": { "cwe_ids": [ "CWE-670" ], "github_reviewed": true, "github_reviewed_at": "2021-10-18T21:06:02Z", "nvd_published_at": "2021-10-18T21:15:00Z", "severity": "HIGH" }, "details": "### Impact \n\nIn `evm` crate `\u003c 0.31.0`, `JUMPI` opcode\u0027s condition is checked after the destination validity check. However, according to Geth and OpenEthereum, the condition check should happen before the destination validity check.\n\n### Patches\n\nThis is a **high** severity security advisory if you use `evm` crate for Ethereum mainnet. In this case, you should update your library dependency immediately to on or after `0.31.0`.\n\nThis is a **low** severity security advisory if you use `evm` crate in Frontier or in a standalone blockchain, because there\u0027s no security exploit possible with this advisory. It is **not** recommended to update to on or after `0.31.0` until all the normal chain upgrade preparations have been done. If you use Frontier or other `pallet-evm` based Substrate blockchain, please ensure to update your `spec_version` before updating this. For other blockchains, please make sure to follow a hard-fork process before you update this.\n\n### Workarounds\n\nIf you are dependent on an older version of `evm` and cannot update due to API interface changes, please contact Wei by email (wei@that.world), who will be happy to help you to publish patch releases for older `evm` versions.\n\n### References\n\nFix PR: https://github.com/rust-blockchain/evm/pull/67\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in the `evm` repo.\n\n### Special thanks\n\nSpecial thanks to @rakita for reporting this issue.\n", "id": "GHSA-pvh2-pj76-4m96", "modified": "2021-10-25T20:07:57Z", "published": "2021-10-19T15:28:35Z", "references": [ { "type": "WEB", "url": "https://github.com/rust-blockchain/evm/security/advisories/GHSA-pvh2-pj76-4m96" }, { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2021-41153" }, { "type": "WEB", "url": "https://github.com/rust-blockchain/evm/pull/67" }, { "type": "PACKAGE", "url": "https://github.com/rust-blockchain/evm" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N", "type": "CVSS_V3" } ], "summary": "Specification non-compliance in JUMPI" }
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.