Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🦀 crates.io

GHSA-773q-5334-5gf9

Memory over-allocation in evm-core

Also known asRUSTSEC-2021-0066
Published
Aug 25, 2021
Updated
Nov 8, 2023
Affected
5 pkgs
Patched
5 / 5
Exploits
None indexed

Blast Radius

5 pkgs affected
🦀evm-core🦀evm-core🦀evm-core🦀evm-core🦀evm-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

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.

The flaw was corrected in commit 19ade85.

Affected Packages

5 total 5 fixed
EcosystemPackageVulnerable rangeFix
🦀crates.ioevm-core0.26.0&&< 0.26.10.26.1
🦀crates.ioevm-core0.25.0&&< 0.25.10.25.1
🦀crates.ioevm-core0.24.0&&< 0.24.10.24.1
🦀crates.ioevm-core0.23.0&&< 0.23.10.23.1
🦀crates.ioevm-coreall versions0.21.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for evm-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update evm-core to 0.26.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-773q-5334-5gf9 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-773q-5334-5gf9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-773q-5334-5gf9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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. The flaw was corrected in commit `19ade85`.
O3 Security · Impact-Aware SCA

Is GHSA-773q-5334-5gf9 in your dependencies?

O3 detects GHSA-773q-5334-5gf9 across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.