Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Evmos vulnerable to exploit of smart contract account and vesting

CVSS 3.1 8.8 HIGHEUVD CVSS 3.1 8.8 CVSS 3.1 · [email protected] · Secondary 8.8 HIGHCVSS 3.1 · [email protected] · Primary 8.1 HIGHCVSS_V3 CVSS_V4 Publisher rating HIGHFixed by github.com/evmos/evmos/v18 19.0.0osv · severity unknownFixed by github.com/evmos/evmos/v19 19.0.0KEV status unknown

cve-program · CVE-2024-39696

Published

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.

Read the publisher's advisory

euvd · EUVD-2024-2400

Published

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.

Read the publisher's advisory

nvd · CVE-2024-39696

Published

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.

Read the publisher's advisory

osv · GHSA-q6hg-6m9x-5g9c

Published

### Summary This advisory board aims to describe two vulnerabilities found in the Evmos codebase: - _Authorization check on the fundVestingAccount_: unauthorized spend of funds. ### Details #### Authorization check on the fundVestingAccount With the current implementation, 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. ### Severity Based on [ImmuneFi Severity Classification System](https://immunefisupport.zendesk.com/hc/en-us/articles/13332717597585-Severity-Classification-System) the severity was evaluated to Critical since the attack could have lead to direct loss of funds. ### Patches The issue has been patched in versions >=V19.0.0

Read the publisher's advisory

osv · GO-2024-2974

Published

Evmos vulnerable to exploit of smart contract account and vesting in github.com/evmos/evmos

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2024-39696

Published

evmos

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "evmos",
                    "product": "evmos",
                    "versions": [
                        {
                            "version": "< 19.0.0",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2024-2400

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Jul 5, 2024, 6:49:22 PM

dateUpdated: Aug 2, 2024, 4:26:15 AM

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2024-39696

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Analyzed

Weakness classifications: CWE-863

Original publisher date fields

published: 2024-07-05T19:15:10.673

lastModified: 2026-06-17T07:42:29.347

1 source CPE criteria · context only
  • cpe:2.3:a:evmos:evmos:*:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-q6hg-6m9x-5g9c

Published

github.com/evmos/evmos/v18

Go

SEMVER · introduced 0 → fixed 19.0.0

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2024-2974

Published

github.com/evmos/evmos

Go

SEMVER · introduced 0

github.com/evmos/evmos/v2

Go

SEMVER · introduced 0

github.com/evmos/evmos/v3

Go

SEMVER · introduced 0

github.com/evmos/evmos/v4

Go

SEMVER · introduced 0

github.com/evmos/evmos/v5

Go

SEMVER · introduced 0

github.com/evmos/evmos/v6

Go

SEMVER · introduced 0

github.com/evmos/evmos/v7

Go

SEMVER · introduced 0

github.com/evmos/evmos/v8

Go

SEMVER · introduced 0

github.com/evmos/evmos/v9

Go

SEMVER · introduced 0

github.com/evmos/evmos/v10

Go

SEMVER · introduced 0

github.com/evmos/evmos/v11

Go

SEMVER · introduced 0

github.com/evmos/evmos/v12

Go

SEMVER · introduced 0

github.com/evmos/evmos/v13

Go

SEMVER · introduced 0

github.com/evmos/evmos/v14

Go

SEMVER · introduced 0

github.com/evmos/evmos/v15

Go

SEMVER · introduced 0

github.com/evmos/evmos/v16

Go

SEMVER · introduced 0

github.com/evmos/evmos/v17

Go

SEMVER · introduced 0

github.com/evmos/evmos/v18

Go

SEMVER · introduced 0

github.com/evmos/evmos/v19

Go

SEMVER · introduced 0 → fixed 19.0.0

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 15:59 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current