Affected versions
Rust / Cargoevm-core
- Affected versions
- <= 0.21.0
- Fixed version
- 0.21.1
Rust / Cargoevm-core
- Affected versions
- = 0.26.0
- Fixed version
- 0.26.1
Rust / Cargoevm-core
- Affected versions
- = 0.25.0
- Fixed version
- 0.25.1
Rust / Cargoevm-core
- Affected versions
- = 0.22.0
- Fixed version
- 0.22.1
Rust / Cargoevm-core
- Affected versions
- = 0.24.0
- Fixed version
- 0.24.1
Rust / Cargoevm-core
- Affected versions
- = 0.23.0
- Fixed version
- 0.23.1
Rust / Cargoevm
- Affected versions
- = 0.25.0
- Fixed version
- 0.25.1
Rust / Cargoevm
- Affected versions
- = 0.22.0
- Fixed version
- 0.22.1
Rust / Cargoevm
- Affected versions
- = 0.23.0
- Fixed version
- 0.23.1
Rust / Cargoevm
- Affected versions
- = 0.24.0
- Fixed version
- 0.24.1
Rust / Cargoevm
- Affected versions
- = 0.26.0
- Fixed version
- 0.26.1
Rust / Cargoevm
- Affected versions
- <= 0.21.0
- Fixed version
- 0.21.1
Exploitation
Description
Impact
Prior to the patch, when executing specific EVM opcodes related to memory operations that use evm_core::Memory::copy_large, the crate can over-allocate memory when it is not needed, making it possible for an attacker to perform denial-of-service attack.
Patches
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.
Workarounds
None. Please upgrade your evm crate version
References
Fix commit: https://github.com/rust-blockchain/evm/commit/19ade858c430ab13eb562764a870ac9f8506f8dd
For more information
If you have any questions or comments about this advisory:
Open an issue in evm repo
Email Wei

