GHSA-773q-5334-5gf9 json
Memory over-allocation in evm-core
published 5y ago modified 3y ago also RUSTSEC-2021-0066
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
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`.
Patch / fix
- crates.io evm-core 0.21.1, 0.23.1, 0.24.1, 0.25.1, 0.26.1
Is GHSA-773q-5334-5gf9 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | evm-core | >=0.26.0, <0.26.1 >=0.25.0, <0.25.1 >=0.24.0, <0.24.1 >=0.23.0, <0.23.1 <0.21.1 >=0.0.0-0, <0.21.1 >=0.22.0-0, <0.23.1 >=0.24.0-0, <0.24.1 >=0.25.0-0, <0.25.1 >=0.26.0-0, <0.26.1 |
0.26.1 0.25.1 0.24.1 0.23.1 0.21.1 |
Classification
- Weakness
-
- CWE-789 Memory Allocation with Excessive Size Value
References
-
github.com
/rust-blockchain/evm/commit/19ade85
web
-
github.com
/rust-blockchain/evm
package, web
-
rustsec.org
/advisories/RUSTSEC-2021-0066.html
web, advisory
-
crates.io
/crates/evm-core
package
Sources
- GitHub Advisory GHSA-773q-5334-5gf9
- OSV RUSTSEC-2021-0066
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.