CVE-2024-32644
Evmos' transaction execution not accounting for all state transition after interaction with precompiles
- Published
- Updated
- Reserved
- Assigned by
- GitHub_M
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.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| GitHub_MCNA (assigner) | 3.1 | Critical9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H |
| NVDNVD · Analyzed | 3.1 | Critical9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.94% · top 39% of all CVEs (7 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: yes · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.1.
Weakness
Affected products
Affected packages
From reviewed advisories of the GitHub Advisory Database.
- Gogithub.com/evmos/evmos/v16GHSA-3fp5-2xwh-fxm6 (opens in a new tab)
- Gogithub.com/evmos/evmos/v5GHSA-3fp5-2xwh-fxm6 (opens in a new tab)
- Gogithub.com/evmos/evmos/v6GHSA-3fp5-2xwh-fxm6 (opens in a new tab)
- Gogithub.com/evmos/evmos/v7GHSA-3fp5-2xwh-fxm6 (opens in a new tab)
- Gogithub.com/tharsis/evmosGHSA-3fp5-2xwh-fxm6 (opens in a new tab)
- Gogithub.com/tharsis/evmos/v2GHSA-3fp5-2xwh-fxm6 (opens in a new tab)
- Gogithub.com/tharsis/evmos/v3GHSA-3fp5-2xwh-fxm6 (opens in a new tab)
- Gogithub.com/tharsis/evmos/v4GHSA-3fp5-2xwh-fxm6 (opens in a new tab)
- Gogithub.com/tharsis/evmos/v5GHSA-3fp5-2xwh-fxm6 (opens in a new tab)
References (3)
- https://github.com/evmos/evmos/security/advisories/GHSA-3fp5-2xwh-fxm6 (opens in a new tab)x_refsource_CONFIRMx_transferred
- https://github.com/evmos/evmos/commit/08982b5ee726b97bc50eaf58d1914829648b6a5f (opens in a new tab)x_refsource_MISCx_transferred
- https://github.com/evmos/evmos/blob/b196a522ba4951890b40992e9f97aa610f8b5f9c/x/evm/statedb/statedb.go#L460-L465 (opens in a new tab)x_refsource_MISCx_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisory GHSA-3fp5-2xwh-fxm6 (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2024-32644)Record last updated .