# CVE-2024-39696: Evmos vulnerable to exploit of smart contract account and vesting > Attackers can drain funds from any account by exploiting a logic flaw in vesting account creation that bypasses authorization checks. - **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 5 Jul 2024 - **Updated:** 2 Aug 2024 - **Also known as:** GHSA-q6hg-6m9x-5g9c, GO-2024-2974 ## What is CVE-2024-39696? CVE-2024-39696 is a high-severity vulnerability in evmos, published on 5 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Evmos is a decentralized Ethereum Virtual Machine chain on the Cosmos Network. Prior to version 19.0.0, a user can create a vesting account with a 3rd party account (EOA or contract) as funder. Then, this user can create an authorization for the contract.CallerAddress, this is the authorization checked in the code. But the funds are taken from the funder address provided in the message. Consequently, the user can fund a vesting account with a 3rd party account without its permission. The funder address can be any address, so this vulnerability can be used to drain all the accounts in the chain. The issue has been patched in version 19.0.0. Weakness: CWE-863 (Incorrect Authorization) ## Which versions are affected by CVE-2024-39696? 21 open source packages ship an affected version, including github.com/evmos/evmos/v18, github.com/evmos/evmos and github.com/evmos/evmos/v10. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/evmos/evmos/v18` | Go | All versions | None | | `github.com/evmos/evmos/v18` | Go | All versions | 19.0.0 | | `github.com/evmos/evmos/v18` | Go | All versions | 19.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/v16` | Go | All versions | None | | `github.com/evmos/evmos/v17` | Go | All versions | None | | `github.com/evmos/evmos/v19` | Go | All versions | 19.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/v6` | Go | All versions | None | | `github.com/evmos/evmos/v7` | Go | All versions | None | | `github.com/evmos/evmos/v8` | Go | All versions | None | | `github.com/evmos/evmos/v9` | Go | All versions | None | Products: Evmos Evmos. ## How do I fix CVE-2024-39696? Upgrade github.com/evmos/evmos/v18 to 19.0.0 or later. ## Is CVE-2024-39696 being exploited? There is no known exploitation of CVE-2024-39696 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-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-39696 and fix it if it is affected. What it is: CVE-2024-39696 is a high-severity vulnerability in evmos, published on 5 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-39696 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/evmos/evmos/v18 (Go): affected all versions; no fix listed - github.com/evmos/evmos/v18 (Go): affected all versions; fixed in 19.0.0 - github.com/evmos/evmos/v18 (Go): affected all versions; fixed in 19.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/v16 (Go): affected all versions; no fix listed - github.com/evmos/evmos/v17 (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-39696/ (Markdown: https://insights.sbomify.com/CVE-2024-39696/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-39696 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-39696 - OSV: https://osv.dev/vulnerability/CVE-2024-39696 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-39696/ Summaries are generated and may contain mistakes; the official description above is the record.