Denial of service via empty memory copy
Published May 12, 2021 · Updated Aug 3, 2024
Resource exhaustion in Rust EVM evm-core allows remote authenticated users to interrupt EVM execution through crafted opcodes. Memory::copy_large continues processing an empty value and expands memory toward the supplied offset or target size instead of returning without allocation. Execution of affected memory-operation opcodes is required, and the resulting excess allocation can exhaust memory and deny EVM execution.
Summary
What happened
Resource exhaustion in Rust EVM evm-core allows remote authenticated users to interrupt EVM execution through crafted opcodes. Memory::copy_large continues processing an empty value and expands memory toward the supplied offset or target size instead of returning without allocation. Execution of affected memory-operation opcodes is required, and the resulting excess allocation can exhaust memory and deny EVM execution.
The record
- CVE
- CVE-2021-29511
- Published
- May 12, 2021
- Updated
- Aug 3, 2024
- Vendor
- rust-ethereum
- Product
- Rust EVM
- Classifications
- CWE-770, T1499.003
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 12, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.21.1
- Affected versionversion== 0.22.0
- Affected versionversion== 0.23.0
- Affected versionversion== 0.24.0
- Affected versionversion== 0.25.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo