Memory over-allocation in evm crate
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 0.21.1, 0.22.1, 0.23.1, 0.24.1, 0.25.1, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- rust-blockchain evm
fixed in 0.21.1
- evmcrates.io
fixed in 0.21.1
- evm-corecrates.io
fixed in 0.21.1
- evmcrates.io
From 0.22.0 · fixed in 0.22.1
- evmcrates.io
From 0.23.0 · fixed in 0.23.1
- evmcrates.io
From 0.24.0 · fixed in 0.24.1
- evmcrates.io
From 0.25.0 · fixed in 0.25.1
- evmcrates.io
From 0.26.0 · fixed in 0.26.1
- evm-corecrates.io
From 0.22.0 · fixed in 0.22.1
- evm-corecrates.io
From 0.23.0 · fixed in 0.23.1
- evm-corecrates.io
From 0.24.0 · fixed in 0.24.1
- evm-corecrates.io
From 0.25.0 · fixed in 0.25.1
- evm-corecrates.io
From 0.26.0 · fixed in 0.26.1