CVE-2024-32644 Evmos' transaction execution not accounting for all state transition after interaction with precompiles
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- No known exploitation · automatable: yes · technical impact: total
Description
Evmos is a scalable, high-throughput Proof-of-Stake EVM blockchain that is fully compatible and interoperable with Ethereum. Prior to 17.0.0, there is a way to mint arbitrary tokens due to the possibility to have two different states not in sync during the execution of a transaction. The exploit is based on the fact that to sync the Cosmos SDK state and the EVM one, we rely on the stateDB.Commit() method. When we call this method, we iterate though all the dirtyStorage and, if and only if it is different than the originStorage, we set the new state. Setting the new state means we update the Cosmos SDK KVStore. If a contract storage state that is the same before and after a transaction, but is changed during the transaction and can call an external contract after the change, it can be exploited to make the transaction similar to non-atomic. The vulnerability is critical since this could lead to drain of funds through creative SC interactions. The issue has been patched in versions >=V17.0.0.
Upgrade path
3 packages: 1 fixed, 2 partially fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| evmos github.com/evmos/evmos(Go) | < 17.0.0; <= 5.0.0; <= 6.0.4; <= 7.0.0 +2 more | 17.0.0 | Partially fixed |
| tharsis github.com/tharsis/evmos(Go) | <= 1.1.3; <= 2.0.2; <= 3.0.3; <= 4.0.2 +2 more | after 1.1.3, 2.0.2, 3.0.3, 4.0.2, 5.0.1 | Partially fixed |
| evmos github.com/evmos/evmos | < 17.0.0; = < 17.0.0 | 17.0.0 | Fixed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| evmos github.com/evmos/evmos(Go) | < 17.0.0 | 17.0.0 |
| evmos github.com/evmos/evmos(Go) | <= 7.0.0 | No fix listed |
| evmos github.com/evmos/evmos(Go) | <= 6.0.4 | No fix listed |
| evmos github.com/evmos/evmos(Go) | <= 5.0.0 | No fix listed |
| tharsis github.com/tharsis/evmos(Go) | <= 1.1.3 | No fix listed |
| tharsis github.com/tharsis/evmos(Go) | <= 2.0.2 | No fix listed |
| tharsis github.com/tharsis/evmos(Go) | <= 3.0.3 | No fix listed |
| tharsis github.com/tharsis/evmos(Go) | <= 4.0.2 | No fix listed |
| tharsis github.com/tharsis/evmos(Go) | <= 5.0.1 | No fix listed |
| evmos github.com/evmos/evmos(Go) | All versions | No fix listed |
| tharsis github.com/tharsis/evmos(Go) | All versions | No fix listed |
| evmos github.com/evmos/evmos(Go) | <= 16.0.4 | No fix listed |
| evmos github.com/evmos/evmos | = < 17.0.0 | No fix listed |
| evmos github.com/evmos/evmos | < 17.0.0 | 17.0.0 |
References
- https://github.com/evmos/evmos/security/advisories/GHSA-3fp5-2xwh-fxm6 vendor-advisory
- nvd.nist.gov third-party-advisory vendor-advisory
- https://github.com/evmos/evmos/commit/08982b5ee726b97bc50eaf58d1914829648b6a5f patch
- github.com product
- github.com
- https://github.com/evmos/evmos/blob/b196a522ba4951890b40992e9f97aa610f8b5f9c/x/evm/statedb/statedb.go#L460-L465 product
- github.com