CVE-2024-32644
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of data tampering, service disruption.
- Exploit odds
- 0.9% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.9% in the next 30 days (EPSS).
- Severity: 9.1 CRITICAL (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.9% · EPSS, next 30 days
- Weakness
- CWE-662
- Record status
- Analyzed
Affected
- Evmos < 17.0.0
Attack profile CVSS 3.1 · 9.1
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2024-32644.md and follow it. Check whether this project is affected by CVE-2024-32644. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/evmos/evmos/commit/08982b5ee726b97bc50eaf58d1914829648b6a5f
- https://github.com/evmos/evmos/security/advisories/GHSA-3fp5-2xwh-fxm6
- https://github.com/evmos/evmos/commit/08982b5ee726b97bc50eaf58d1914829648b6a5f
- https://github.com/evmos/evmos/security/advisories/GHSA-3fp5-2xwh-fxm6
References
- https://github.com/evmos/evmos/blob/b196a522ba4951890b40992e9f97aa610f8b5f9c/x/evm/statedb/statedb.go#L460-L465
- https://github.com/evmos/evmos/commit/08982b5ee726b97bc50eaf58d1914829648b6a5f
- https://github.com/evmos/evmos/security/advisories/GHSA-3fp5-2xwh-fxm6
- https://github.com/evmos/evmos/blob/b196a522ba4951890b40992e9f97aa610f8b5f9c/x/evm/statedb/statedb.go#L460-L465
- https://github.com/evmos/evmos/commit/08982b5ee726b97bc50eaf58d1914829648b6a5f
- https://github.com/evmos/evmos/security/advisories/GHSA-3fp5-2xwh-fxm6