# CVE-2024-37154: Evmos allows unvested token delegations > Attackers can delegate unvested tokens in Evmos, bypassing vesting restrictions and gaining unauthorized control over funds. - **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 6 Jun 2024 - **Updated:** 2 Aug 2024 - **Also known as:** GHSA-7hrh-v6wp-53vw, GO-2024-2904 ## What is CVE-2024-37154? CVE-2024-37154 is a medium-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. Users are able to delegate tokens that have not yet been vested. This affects employees and grantees who have funds managed via `ClawbackVestingAccount`. This affects 18.1.0 and earlier. Weakness: CWE-863 (Incorrect Authorization), CWE-285 (Improper Authorization) ## Which versions are affected by CVE-2024-37154? 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 to 10.0.1 | None | | `github.com/evmos/evmos/v10` | Go | All versions to 10.0.1 | None | | `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 to 11.0.2 | None | | `github.com/evmos/evmos/v11` | Go | All versions to 11.0.2 | None | | `github.com/evmos/evmos/v12` | Go | All versions | None | | `github.com/evmos/evmos/v12` | Go | All versions to 12.1.6 | None | | `github.com/evmos/evmos/v12` | Go | All versions to 12.1.6 | None | | `github.com/evmos/evmos/v13` | Go | All versions | None | | `github.com/evmos/evmos/v13` | Go | All versions to 13.0.2 | None | | `github.com/evmos/evmos/v13` | Go | All versions to 13.0.2 | None | | `github.com/evmos/evmos/v14` | Go | All versions | None | | `github.com/evmos/evmos/v14` | Go | All versions to 14.1.0 | None | | `github.com/evmos/evmos/v14` | Go | All versions to 14.1.0 | None | | `github.com/evmos/evmos/v15` | Go | All versions | None | | `github.com/evmos/evmos/v15` | Go | All versions to 15.0.0 | None | | `github.com/evmos/evmos/v15` | Go | All versions to 15.0.0 | None | | `github.com/evmos/evmos/v16` | Go | All versions | None | | `github.com/evmos/evmos/v16` | Go | All versions to 16.0.4 | None | | `github.com/evmos/evmos/v16` | Go | All versions to 16.0.4 | None | | `github.com/evmos/evmos/v17` | Go | All versions | None | | `github.com/evmos/evmos/v17` | Go | All versions to 17.0.1 | None | | `github.com/evmos/evmos/v17` | Go | All versions to 17.0.1 | None | | `github.com/evmos/evmos/v18` | Go | All versions | None | | `github.com/evmos/evmos/v18` | Go | All versions to 18.1.0 | None | | `github.com/evmos/evmos/v18` | Go | All versions to 18.1.0 | None | | `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 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/v8` | Go | All versions to 8.2.3 | None | Products: Evmos Evmos. ## How do I fix CVE-2024-37154? No fix has been published for CVE-2024-37154 yet. Limit exposure of the affected software until one is available. ## Is CVE-2024-37154 being exploited? There is no known exploitation of CVE-2024-37154 in the wild and no public exploit code. ## 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-37153](https://insights.sbomify.com/CVE-2024-37153/): Evmos's contract balance not updating correctly after interchain transaction (high 7.5) - [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-37154 and fix it if it is affected. What it is: CVE-2024-37154 is a medium-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: There is no known exploitation of CVE-2024-37154 in the wild and no public exploit code. 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 up to 10.0.1; no fix listed - github.com/evmos/evmos/v10 (Go): affected all versions up to 10.0.1; no fix listed - 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 up to 11.0.2; no fix listed - github.com/evmos/evmos/v11 (Go): affected all versions up to 11.0.2; no fix listed - github.com/evmos/evmos/v12 (Go): affected all versions; no fix listed - github.com/evmos/evmos/v12 (Go): affected all versions up to 12.1.6; no fix listed - github.com/evmos/evmos/v12 (Go): affected all versions up to 12.1.6; no fix listed - github.com/evmos/evmos/v13 (Go): affected all versions; no fix listed - github.com/evmos/evmos/v13 (Go): affected all versions up to 13.0.2; 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-37154/ (Markdown: https://insights.sbomify.com/CVE-2024-37154/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-37154 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-37154 - OSV: https://osv.dev/vulnerability/CVE-2024-37154 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-37154/ Summaries are generated and may contain mistakes; the official description above is the record.