Skip to content

Specification non-compliance in JUMPI

High severity GitHub Reviewed Published Oct 18, 2021 in rust-ethereum/evm • Updated Feb 1, 2023

Package

cargo evm (Rust)

Affected versions

< 0.31.0

Patched versions

0.31.0

Description

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 ([email protected]), who will be happy to help you to publish patch releases for older evm versions.

References

Fix PR: rust-ethereum/evm#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.

References

@sorpaas sorpaas published to rust-ethereum/evm Oct 18, 2021
Reviewed Oct 18, 2021
Published by the National Vulnerability Database Oct 18, 2021
Published to the GitHub Advisory Database Oct 19, 2021
Last updated Feb 1, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N

EPSS score

0.217%
(60th percentile)

Weaknesses

CVE ID

CVE-2021-41153

GHSA ID

GHSA-pvh2-pj76-4m96

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.