CVE-2024-21629
Evm Project Evm vulnerability
Rust EVM is an Ethereum Virtual Machine interpreter. In `rust-evm`, a feature called `record_external_operation` was introduced, allowing library users to record custom gas changes. This feature can have some bogus interactions with the call stack. In particular, during finalization of a `CREATE` or `CREATE2`, in the case that the substack execution happens successfully, `rust-evm` will first commit the substate, and then call `record_external_operation(Write(out_code.len()))`. If `record_external_operation` later fails, this error is returned to the parent call stack, instead of `Succeeded`. Yet, the substate commitment already happened. This causes smart contracts able to commit state changes, when the parent caller contract receives zero address (which usually indicates that the execution has failed). This issue only impacts library users with custom `record_external_operation` that returns errors. The issue is patched in release 0.41.1. No known workarounds are available.
Affected products
Evm. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Evm Project Evm runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/rust-ethereum/evm/security/advisories/GHSA-27wg-99g8-2v4v · Vendor Advisory
- github.com/rust-ethereum/evm/commit/d8991ec727ad0fb64fe9957a3cd307387a6701e4 · Patch
- github.com/rust-ethereum/evm/pull/264 · Patch
- github.com/rust-ethereum/evm/blob/release-v041/src/executor/stack/executor.rs#L1012C25-L10
- nvd.nist.gov/vuln/detail/CVE-2024-21629
- cve.org/CVERecord?id=CVE-2024-21629
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.