{"id":"EUVD-2024-1080","enisaUuid":"baa1d4a6-2002-32c5-801b-3c7b2f6dcc75","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 \u003e\u003dV17.0.0.","datePublished":"Apr 19, 2024, 2:53:44 PM","dateUpdated":"Aug 2, 2024, 2:13:40 AM","baseScore":9.1,"baseScoreVersion":"3.1","baseScoreVector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H","references":"https://github.com/evmos/evmos/security/advisories/GHSA-3fp5-2xwh-fxm6\nhttps://github.com/evmos/evmos/commit/08982b5ee726b97bc50eaf58d1914829648b6a5f\nhttps://github.com/evmos/evmos/blob/b196a522ba4951890b40992e9f97aa610f8b5f9c/x/evm/statedb/statedb.go#L460-L465\n","aliases":"CVE-2024-32644\nGHSA-3fp5-2xwh-fxm6\n","assigner":"GitHub_M","epss":0.94,"enisaIdProduct":[{"id":"6508c7c9-e30b-3564-beb3-55562775d8d7","product":{"name":"evmos","vendor":{"name":"tharsis"}},"product_version":"\u003c 17.0.0"},{"id":"b45a2b97-d0a7-3515-a141-17961602024e","product":{"name":"evmos","vendor":{"name":"tharsis"}}}],"enisaIdVendor":[{"id":"b45a2b97-d0a7-3515-a141-17961602024e","vendor":{"name":"evmos"}}],"enisaIdVulnerability":[{"id":"1143aa40-df3f-31da-a07b-7101e9e4bbb3","vulnerability":{"id":"CVE-2024-32644","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 \u003e\u003dV17.0.0.","datePublished":"Apr 19, 2024, 2:53:44 PM","dateUpdated":"Aug 2, 2024, 2:13:40 AM","status":"PUBLISHED","baseScore":9.1,"baseScoreVersion":"3.1","baseScoreVector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H","references":"https://github.com/evmos/evmos/security/advisories/GHSA-3fp5-2xwh-fxm6\nhttps://github.com/evmos/evmos/commit/08982b5ee726b97bc50eaf58d1914829648b6a5f\nhttps://github.com/evmos/evmos/blob/b196a522ba4951890b40992e9f97aa610f8b5f9c/x/evm/statedb/statedb.go#L460-L465\n","enisa_id":"EUVD-2024-1080\n","assigner":"GitHub_M","epss":0.94,"dataProcessed":"Nov 13, 2026, 7:19:11 AM","vulnerabilityProduct":[{"id":"93351036-8517-49f9-8453-03b24a8627ac","product":{"name":"evmos","vendor":{"name":"tharsis"}},"product_version":"\u003c 17.0.0"},{"id":"ba2eac79-09e0-365f-b963-3b594935a07e","product":{"name":"evmos","vendor":{"name":"tharsis"}},"product_version":"\u003c 17.0.0"}],"vulnerabilityVendor":[{"id":"de5370b7-2c90-3e2d-899c-45b9e4a46705","vendor":{"name":"evmos"}}]}},{"id":"68f5f2df-ee1d-3f2d-883c-4caae2eb42f1","vulnerability":{"id":"GHSA-3fp5-2xwh-fxm6","description":"Evmos transaction execution not accounting for all state transition after interaction with precompiles","datePublished":"Apr 10, 2024, 10:04:30 PM","dateUpdated":"Apr 19, 2024, 4:20:58 PM","baseScore":null,"references":"https://github.com/evmos/evmos/security/advisories/GHSA-3fp5-2xwh-fxm6\nhttps://nvd.nist.gov/vuln/detail/CVE-2024-32644\nhttps://github.com/evmos/evmos/commit/08982b5ee726b97bc50eaf58d1914829648b6a5f\nhttps://github.com/evmos/evmos\nhttps://github.com/evmos/evmos/blob/b196a522ba4951890b40992e9f97aa610f8b5f9c/x/evm/statedb/state_object.go#L53-L68\nhttps://github.com/evmos/evmos/blob/b196a522ba4951890b40992e9f97aa610f8b5f9c/x/evm/statedb/statedb.go#L33-L55\nhttps://github.com/evmos/evmos/blob/b196a522ba4951890b40992e9f97aa610f8b5f9c/x/evm/statedb/statedb.go#L460-L465\n","enisa_id":"EUVD-2024-1080\n","aliases":"CVE-2024-32644\nGHSA-3fp5-2xwh-fxm6\n","epss":0.0,"dataProcessed":"Nov 9, 2026, 3:34:28 PM","vulnerabilityProduct":[],"vulnerabilityVendor":[]}}],"enisaIdAdvisory":[]}