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 allows transferring unvested tokens after delegations

CVSS 3.1 3.5 LOWCVSS 3.1 3.5 LOWCVSS 3.1 3.5 LOWEUVD CVSS 3.1 3.5 EUVD CVSS 3.1 3.5 EUVD CVSS 3.1 3.5 CVSS 3.1 · [email protected] · Secondary 3.5 LOWCVSS 3.1 · [email protected] · Primary 4.3 MEDIUMCVSS 3.1 · [email protected] · Secondary 3.5 LOWCVSS 3.1 · [email protected] · Primary 8.1 HIGHCVSS 3.1 · [email protected] · Secondary 3.5 LOWCVSS 3.1 · [email protected] · Primary 6.5 MEDIUMCVSS_V3 Publisher rating LOWFixed by github.com/evmos/evmos/v17 18.0.0Fixed by github.com/evmos/evmos/v16 18.0.0Fixed by github.com/evmos/evmos/v15 18.0.0Fixed by github.com/evmos/evmos/v14 18.0.0osv · severity unknownFixed by github.com/evmos/evmos/v18 18.0.0osv · severity unknownFixed by github.com/evmos/evmos/v18 18.0.0osv · severity unknownFixed by github.com/evmos/evmos/v18 18.0.0KEV status unknown

cve-program · CVE-2024-32873

Published

Evmos is the Ethereum Virtual Machine (EVM) Hub on the Cosmos Network. The spendable balance is not updated properly when delegating vested tokens. The issue allows a clawback vesting account to anticipate the release of unvested tokens. This vulnerability is fixed in 18.0.0.

Read the publisher's advisory

cve-program · CVE-2024-37158

Published

Evmos is the Ethereum Virtual Machine (EVM) Hub on the Cosmos Network. Preliminary checks on actions computed by the clawback vesting accounts are performed in the ante handler. Evmos core, implements two different ante handlers: one for Cosmos transactions and one for Ethereum transactions. Checks performed on the two implementation are different. The vulnerability discovered allowed a clawback account to bypass Cosmos ante handler checks by sending an Ethereum transaction targeting a precompile used to interact with a Cosmos SDK module. This vulnerability is fixed in 18.0.0.

Read the publisher's advisory

cve-program · CVE-2024-37159

Published

Evmos is the Ethereum Virtual Machine (EVM) Hub on the Cosmos Network. This vulnerability allowed a user to create a validator using vested tokens to deposit the self-bond. This vulnerability is fixed in 18.0.0.

Read the publisher's advisory

euvd · EUVD-2024-2129

Published

Evmos is the Ethereum Virtual Machine (EVM) Hub on the Cosmos Network. The spendable balance is not updated properly when delegating vested tokens. The issue allows a clawback vesting account to anticipate the release of unvested tokens. This vulnerability is fixed in 18.0.0.

Read the publisher's advisory

euvd · EUVD-2024-36470

Published

Evmos is the Ethereum Virtual Machine (EVM) Hub on the Cosmos Network. Preliminary checks on actions computed by the clawback vesting accounts are performed in the ante handler. Evmos core, implements two different ante handlers: one for Cosmos transactions and one for Ethereum transactions. Checks performed on the two implementation are different. The vulnerability discovered allowed a clawback account to bypass Cosmos ante handler checks by sending an Ethereum transaction targeting a precompile used to interact with a Cosmos SDK module. This vulnerability is fixed in 18.0.0.

Read the publisher's advisory

euvd · EUVD-2024-36471

Published

Evmos is the Ethereum Virtual Machine (EVM) Hub on the Cosmos Network. This vulnerability allowed a user to create a validator using vested tokens to deposit the self-bond. This vulnerability is fixed in 18.0.0.

Read the publisher's advisory

nvd · CVE-2024-32873

Published

Evmos is the Ethereum Virtual Machine (EVM) Hub on the Cosmos Network. The spendable balance is not updated properly when delegating vested tokens. The issue allows a clawback vesting account to anticipate the release of unvested tokens. This vulnerability is fixed in 18.0.0.

Read the publisher's advisory

nvd · CVE-2024-37158

Published

Evmos is the Ethereum Virtual Machine (EVM) Hub on the Cosmos Network. Preliminary checks on actions computed by the clawback vesting accounts are performed in the ante handler. Evmos core, implements two different ante handlers: one for Cosmos transactions and one for Ethereum transactions. Checks performed on the two implementation are different. The vulnerability discovered allowed a clawback account to bypass Cosmos ante handler checks by sending an Ethereum transaction targeting a precompile used to interact with a Cosmos SDK module. This vulnerability is fixed in 18.0.0.

Read the publisher's advisory

nvd · CVE-2024-37159

Published

Evmos is the Ethereum Virtual Machine (EVM) Hub on the Cosmos Network. This vulnerability allowed a user to create a validator using vested tokens to deposit the self-bond. This vulnerability is fixed in 18.0.0.

Read the publisher's advisory

osv · GHSA-pxv8-qhrh-jc7v

Published

## Impact This advisory has been created to address the following vulnerabilities found in the Evmos codebase and affecting vesting accounts. ### Wrong spendable balance computation The spendable balance is not updated properly when delegating vested tokens. The following example help in describing the issue: - Given a clawback vesting account with a starting `15M` vesting schedule. The initial spendable balance is `0`. - Time passes and `5M` are vested. The spendable balance is now `5M`. - The account delegate `5M`. The spendable balance should be `0`, but returns `5M` - The account can send `5M` to another account. The issue allowed a clawback vesting account to anticipate the release of unvested tokens. ### Missing precompile checks Preliminary checks on actions computed by the clawback vesting accounts are performed in the ante handler. Evmos core, implements two different ante handlers: one for Cosmos transactions and one for Ethereum transactions. Checks performed on the two implementation are different. The vulnerability discovered allowed a clawback account to bypass Cosmos ante handler checks by sending an Ethereum transaction targeting a precompile used to interact with a Cosmos SDK module. ### Missing create validator check This vulnerability allowed a user to create a validator using vested tokens to deposit the self-bond. ## Patches - The spendable balance function has been fixed correcting the `TrackDelegation` function. - The checks for the staking module, for the delegation and the create validator, has been moved into the `MsgServer` of a wrapper around the Cosmos SDK staking module. The issues have been patched in versions >=V18.0.0. ## References 1. [Evmos vesting module](https://docs.evmos.org/protocol/modules/vesting) ## For more information If you have any questions or comments about this advisory: Reach out to the Core Team in [Discord](https://discord.gg/evmos) Open a discussion in [evmos/evmos](https://github.com/evmos/evmos/discussions) Email us at [[email protected]](mailto:[email protected]) for security questions

Read the publisher's advisory

osv · GO-2024-2891

Published

evmos allows transferring unvested tokens after delegations in github.com/evmos/evmos

Read the publisher's advisory

osv · GO-2024-2926

Published

Evmos is missing precompile checks in github.com/evmos/evmos

Read the publisher's advisory

osv · GO-2024-2927

Published

Evmos is missing create validator check in github.com/evmos/evmos

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2024-32873

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": "< 18.0.0",
                            "status": "affected"
                        }
                    ]
                }

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

cve-program · CVE-2024-37158

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": "< 18.0.0",
                            "status": "affected"
                        }
                    ]
                }

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

cve-program · CVE-2024-37159

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": "< 18.0.0",
                            "status": "affected"
                        }
                    ]
                }

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

euvd · EUVD-2024-2129

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: Jun 6, 2024, 6:13:54 PM

dateUpdated: Aug 2, 2024, 2:20:35 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

euvd · EUVD-2024-36470

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: Jun 17, 2024, 2:03:22 PM

dateUpdated: Aug 2, 2024, 3:50:54 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

euvd · EUVD-2024-36471

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: Jun 17, 2024, 2:03:29 PM

dateUpdated: Aug 2, 2024, 3:50:55 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-32873

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: Modified

Weakness classifications: CWE-682

Original publisher date fields

published: 2024-06-06T19:15:56.390

lastModified: 2026-06-17T07:30:35.707

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

nvd · CVE-2024-37158

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-691 · NVD-CWE-noinfo

Original publisher date fields

published: 2024-06-17T14:15:10.430

lastModified: 2026-06-17T07:37:51.953

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

nvd · CVE-2024-37159

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-285 · NVD-CWE-noinfo

Original publisher date fields

published: 2024-06-17T14:15:10.693

lastModified: 2026-06-17T07:37:52.063

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-pxv8-qhrh-jc7v

Published

github.com/evmos/evmos/v17

Go

SEMVER · introduced 0 → fixed 18.0.0

github.com/evmos/evmos/v16

Go

SEMVER · introduced 0 → fixed 18.0.0

github.com/evmos/evmos/v15

Go

SEMVER · introduced 0 → fixed 18.0.0

github.com/evmos/evmos/v14

Go

SEMVER · introduced 0 → fixed 18.0.0

github.com/evmos/evmos/v13

Go

SEMVER · introduced 0 → fixed 18.0.0

github.com/evmos/evmos/v12

Go

SEMVER · introduced 0 → fixed 18.0.0

github.com/evmos/evmos/v11

Go

SEMVER · introduced 0 → fixed 18.0.0

github.com/evmos/evmos/v10

Go

SEMVER · introduced 0 → fixed 18.0.0

github.com/evmos/evmos/v9

Go

SEMVER · introduced 0 → fixed 18.0.0

github.com/evmos/evmos/v8

Go

SEMVER · introduced 0 → fixed 18.0.0

github.com/evmos/evmos/v7

Go

SEMVER · introduced 0 → fixed 18.0.0

github.com/evmos/evmos/v6

Go

SEMVER · introduced 0 → fixed 18.0.0

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

osv · GO-2024-2891

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 → fixed 18.0.0

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

osv · GO-2024-2926

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 → fixed 18.0.0

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

osv · GO-2024-2927

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 → fixed 18.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 14:56 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current