# CVE-2024-37153: Evmos's contract balance not updating correctly after interchain transaction > Attackers can exploit a logic flaw in Evmos to double token supply via interchain transactions, requiring an upgrade to patched versions. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 6 Jun 2024 - **Updated:** 2 Aug 2024 - **Also known as:** GHSA-xgr7-jgq3-mhmc, GO-2024-2903 ## What is CVE-2024-37153? CVE-2024-37153 is a high-severity vulnerability in evmos, published on 6 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Evmos is the Ethereum Virtual Machine (EVM) Hub on the Cosmos Network. There is an issue with how to liquid stake using Safe which itself is a contract. The bug only appears when there is a local state change together with an ICS20 transfer in the same function and uses the contract's balance, that is using the contract address as the sender parameter in an ICS20 transfer using the ICS20 precompile. This is in essence the "infinite money glitch" allowing contracts to double the supply of Evmos after each transaction.The issue has been patched in versions >=V18.1.0. Weakness: CWE-670 (Always-Incorrect Control Flow Implementation) ## Which versions are affected by CVE-2024-37153? 40 open source packages ship an affected version, including github.com/evmos/evmos/v10, github.com/evmos/evmos and github.com/evmos/evmos/v11. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/evmos/evmos/v10` | Go | All versions | None | | `github.com/evmos/evmos/v10` | Go | All versions | 18.1.0 | | `github.com/evmos/evmos/v10` | Go | All versions | 18.1.0 | | `github.com/evmos/evmos` | Go | All versions | None | | `github.com/evmos/evmos/v11` | Go | All versions | None | | `github.com/evmos/evmos/v11` | Go | All versions | 18.1.0 | | `github.com/evmos/evmos/v11` | Go | All versions | 18.1.0 | | `github.com/evmos/evmos/v12` | Go | All versions | None | | `github.com/evmos/evmos/v12` | Go | All versions | 18.1.0 | | `github.com/evmos/evmos/v12` | Go | All versions | 18.1.0 | | `github.com/evmos/evmos/v13` | Go | All versions | None | | `github.com/evmos/evmos/v13` | Go | All versions | 18.1.0 | | `github.com/evmos/evmos/v13` | Go | All versions | 18.1.0 | | `github.com/evmos/evmos/v14` | Go | All versions | None | | `github.com/evmos/evmos/v14` | Go | All versions | 18.1.0 | | `github.com/evmos/evmos/v14` | Go | All versions | 18.1.0 | | `github.com/evmos/evmos/v15` | Go | All versions | None | | `github.com/evmos/evmos/v15` | Go | All versions | 18.1.0 | | `github.com/evmos/evmos/v15` | Go | All versions | 18.1.0 | | `github.com/evmos/evmos/v16` | Go | All versions | None | | `github.com/evmos/evmos/v16` | Go | All versions | 18.1.0 | | `github.com/evmos/evmos/v16` | Go | All versions | 18.1.0 | | `github.com/evmos/evmos/v17` | Go | All versions | None | | `github.com/evmos/evmos/v17` | Go | All versions | 18.1.0 | | `github.com/evmos/evmos/v17` | Go | All versions | 18.1.0 | | `github.com/evmos/evmos/v18` | Go | All versions | 18.1.0 | | `github.com/evmos/evmos/v18` | Go | All versions | 18.1.0 | | `github.com/evmos/evmos/v18` | Go | All versions | 18.1.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/v6` | Go | All versions | None | | `github.com/evmos/evmos/v6` | Go | All versions | 18.1.0 | | `github.com/evmos/evmos/v6` | Go | All versions | 18.1.0 | | `github.com/evmos/evmos/v7` | Go | All versions | None | | `github.com/evmos/evmos/v7` | Go | All versions | 18.1.0 | | `github.com/evmos/evmos/v7` | Go | All versions | 18.1.0 | | `github.com/evmos/evmos/v8` | Go | All versions | None | | `github.com/evmos/evmos/v8` | Go | All versions | 18.1.0 | Products: Evmos Evmos. ## How do I fix CVE-2024-37153? Upgrade github.com/evmos/evmos/v10 to 18.1.0 or later. ## Is CVE-2024-37153 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-37153 exists. ## Other vulnerabilities in evmos - [CVE-2024-32644](https://insights.sbomify.com/CVE-2024-32644/): Evmos' transaction execution not accounting for all state transition after interaction with precompiles (critical 9.1) - [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-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-37153 and fix it if it is affected. What it is: CVE-2024-37153 is a high-severity vulnerability in evmos, published on 6 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-37153 exists. Affected packages and fixed versions: - github.com/evmos/evmos/v10 (Go): affected all versions; no fix listed - github.com/evmos/evmos/v10 (Go): affected all versions; fixed in 18.1.0 - github.com/evmos/evmos/v10 (Go): affected all versions; fixed in 18.1.0 - github.com/evmos/evmos (Go): affected all versions; no fix listed - github.com/evmos/evmos/v11 (Go): affected all versions; no fix listed - github.com/evmos/evmos/v11 (Go): affected all versions; fixed in 18.1.0 - github.com/evmos/evmos/v11 (Go): affected all versions; fixed in 18.1.0 - github.com/evmos/evmos/v12 (Go): affected all versions; no fix listed - github.com/evmos/evmos/v12 (Go): affected all versions; fixed in 18.1.0 - github.com/evmos/evmos/v12 (Go): affected all versions; fixed in 18.1.0 - github.com/evmos/evmos/v13 (Go): affected all versions; no fix listed - github.com/evmos/evmos/v13 (Go): affected all versions; fixed in 18.1.0 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-37153/ (Markdown: https://insights.sbomify.com/CVE-2024-37153/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-37153 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-37153 - OSV: https://osv.dev/vulnerability/CVE-2024-37153 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-37153/ Summaries are generated and may contain mistakes; the official description above is the record.