Vulnerability in evm (CVE-2021-29511)
Summary
Vulnerability in evm (CVE-2021-29511). Risk of unauthorized operations or information disclosure. Exploitable via evm. Mitigation: upgrade to 0.26.1 or later.
Original description
The description as published by the source.
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:
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-29511 has been found in evm.
Attackers can target a specific entry point like evm over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade evm to 0.26.1 or later.
If unsure, ask your IT team or search "evm CVE-2021-29511" on the vendor's site.
CVE-2021-29511 (evm) — CWE-770
Attack vector: remote (network-reachable) / no user interaction
Attack surface: evm
Patched: 0.26.1 — apply immediately
Workaround: None.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-770) exists in evm. Attackers reach the vulnerable code path via evm.
Check the vendor advisory for the affected versions of evm. Attack surface: evm.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.26.1.
Workaround: None.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'evm' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'evm' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
evmを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
None.パッチが適用されるまでの応急処置として、None. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade evm to 0.26.1ステージング環境で 0.26.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web github.com
- web github.com