# CVE-2024-32644: Evmos' transaction execution not accounting for all state transition after interaction with precompiles > Attackers can mint arbitrary tokens or drain funds by exploiting state synchronization flaws between Cosmos SDK and EVM during transaction execution. - **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 19 Apr 2024 - **Updated:** 2 Aug 2024 - **Also known as:** GHSA-3fp5-2xwh-fxm6, GO-2024-2715 ## What is CVE-2024-32644? CVE-2024-32644 is a critical vulnerability in evmos, published on 19 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-662 (Improper Synchronization) ## Which versions are affected by CVE-2024-32644? 40 open source packages ship an affected version, including github.com/evmos/evmos/v16, github.com/evmos/evmos and github.com/evmos/evmos/v10. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/evmos/evmos/v16` | Go | All versions | None | | `github.com/evmos/evmos/v16` | Go | All versions | 17.0.0 | | `github.com/evmos/evmos/v16` | Go | All versions | 17.0.0 | | `github.com/evmos/evmos` | Go | All versions | None | | `github.com/evmos/evmos/v10` | Go | All versions | None | | `github.com/evmos/evmos/v11` | Go | All versions | None | | `github.com/evmos/evmos/v12` | Go | All versions | None | | `github.com/evmos/evmos/v13` | Go | All versions | None | | `github.com/evmos/evmos/v14` | Go | All versions | None | | `github.com/evmos/evmos/v15` | Go | All versions | None | | `github.com/evmos/evmos/v17` | Go | All versions | 17.0.0 | | `github.com/evmos/evmos/v2` | Go | All versions | None | | `github.com/evmos/evmos/v3` | Go | All versions | None | | `github.com/evmos/evmos/v4` | Go | All versions | None | | `github.com/evmos/evmos/v5` | Go | All versions | None | | `github.com/evmos/evmos/v5` | Go | All versions to 5.0.0 | None | | `github.com/evmos/evmos/v5` | Go | All versions to 5.0.0 | None | | `github.com/evmos/evmos/v6` | Go | All versions | None | | `github.com/evmos/evmos/v6` | Go | All versions to 6.0.4 | None | | `github.com/evmos/evmos/v6` | Go | All versions to 6.0.4 | None | | `github.com/evmos/evmos/v7` | Go | All versions | None | | `github.com/evmos/evmos/v7` | Go | All versions to 7.0.0 | None | | `github.com/evmos/evmos/v7` | Go | All versions to 7.0.0 | None | | `github.com/evmos/evmos/v8` | Go | All versions | None | | `github.com/evmos/evmos/v9` | Go | All versions | None | | `github.com/tharsis/evmos` | Go | All versions | None | | `github.com/tharsis/evmos` | Go | All versions to 1.1.3 | None | | `github.com/tharsis/evmos` | Go | All versions to 1.1.3 | None | | `github.com/tharsis/evmos/v2` | Go | All versions | None | | `github.com/tharsis/evmos/v2` | Go | All versions to 2.0.2 | None | | `github.com/tharsis/evmos/v2` | Go | All versions to 2.0.2 | None | | `github.com/tharsis/evmos/v3` | Go | All versions | None | | `github.com/tharsis/evmos/v3` | Go | All versions to 3.0.3 | None | | `github.com/tharsis/evmos/v3` | Go | All versions to 3.0.3 | None | | `github.com/tharsis/evmos/v4` | Go | All versions | None | | `github.com/tharsis/evmos/v4` | Go | All versions to 4.0.2 | None | | `github.com/tharsis/evmos/v4` | Go | All versions to 4.0.2 | None | | `github.com/tharsis/evmos/v5` | Go | All versions | None | | `github.com/tharsis/evmos/v5` | Go | All versions to 5.0.1 | None | | `github.com/tharsis/evmos/v5` | Go | All versions to 5.0.1 | None | Products: Evmos Evmos. ## How do I fix CVE-2024-32644? Upgrade github.com/evmos/evmos/v16 to 17.0.0 or later. ## Is CVE-2024-32644 being exploited? There is no known exploitation of CVE-2024-32644 in the wild and no public exploit code. ## Other vulnerabilities in evmos - [CVE-2024-39696](https://insights.sbomify.com/CVE-2024-39696/): Evmos vulnerable to exploit of smart contract account and vesting (high 8.8) - [CVE-2022-24738](https://insights.sbomify.com/CVE-2022-24738/): Account compromise in Evmos (high 8.1) - [CVE-2024-37153](https://insights.sbomify.com/CVE-2024-37153/): Evmos's contract balance not updating correctly after interchain transaction (high 7.5) - [CVE-2024-37154](https://insights.sbomify.com/CVE-2024-37154/): Evmos allows unvested token delegations (medium 5.3) - [CVE-2024-37158](https://insights.sbomify.com/CVE-2024-37158/): Evmos is missing precompile checks (low 3.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-32644 and fix it if it is affected. What it is: CVE-2024-32644 is a critical vulnerability in evmos, published on 19 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-32644 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/evmos/evmos/v16 (Go): affected all versions; no fix listed - github.com/evmos/evmos/v16 (Go): affected all versions; fixed in 17.0.0 - github.com/evmos/evmos/v16 (Go): affected all versions; fixed in 17.0.0 - github.com/evmos/evmos (Go): affected all versions; no fix listed - github.com/evmos/evmos/v10 (Go): affected all versions; no fix listed - github.com/evmos/evmos/v11 (Go): affected all versions; no fix listed - github.com/evmos/evmos/v12 (Go): affected all versions; no fix listed - github.com/evmos/evmos/v13 (Go): affected all versions; no fix listed - github.com/evmos/evmos/v14 (Go): affected all versions; no fix listed - github.com/evmos/evmos/v15 (Go): affected all versions; no fix listed - github.com/evmos/evmos/v17 (Go): affected all versions; fixed in 17.0.0 - github.com/evmos/evmos/v2 (Go): affected all versions; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-32644/ (Markdown: https://insights.sbomify.com/CVE-2024-32644/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-32644 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-32644 - OSV: https://osv.dev/vulnerability/CVE-2024-32644 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-32644/ Summaries are generated and may contain mistakes; the official description above is the record.