Memory over-allocation in evm crate
rust-blockchain evm
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| evm crates.io |
|
|
rust-blockchain evm
| Product | Affected | Fixed in |
|---|---|---|
| evm crates.io |
|
|
0.23.10.24.10.25.10.26.1| evm-core crates.io |
|
|
evm is a pure Rust implementation of Ethereum Virtual Machine. Prior to the patch, when executing specific EVM opcodes related to memory operations that use `evm_core::Memory::copy_large`, the `evm` crate can over-allocate memory when it is not needed, making it possible for an attacker to perform denial-of-service attack. The flaw was corrected in commit `19ade85`. Users should upgrade to `==0.21.1, ==0.23.1, ==0.24.1, ==0.25.1, >=0.26.1`. There are no workarounds. Please upgrade your `evm` crate version.
From the CVE record · GitHub_M
The evm crate can allocate unnecessary memory when specific EVM opcodes use evm_core::Memory::copy_large. An attacker can exploit this during opcode execution to cause a denial of service. The input does not specify whether network access, authentication, or user interaction is required.
Engineers using crates.io evm or evm-core should check installations below 0.21.1 or in the 0.22.0–0.22.1, 0.23.0–0.23.1, 0.24.0–0.24.1, 0.25.0–0.25.1, or 0.26.0–0.26.1 ranges, excluding each range’s upper endpoint.