dbcve.org
EvmosApplication

CVE-2024-37154

MEDIUM · 5.3 CVSS v3.1 Published 2024-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The vulnerability allows users with ClawbackVestingAccount to delegate tokens that have not yet vested, violating the intended vesting schedule. This authorization failure permits delegation of unvested funds, which should only be allowed on vested tokens.

MitigationUpgrade to version 18.1.1 or later which properly validates token vesting status before permitting delegation operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
EvmosApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Evmos version
    Run 'evmosd version' or check the binary version to determine if it is below 18.1.1
    Affected if The installed version is any version below 18.1.1 (all versions are affected)
  2. Confirm ClawbackVestingAccount module is enabled
    Inspect the module configuration or genesis file for the presence and status of the vesting module
    Affected if ClawbackVestingAccount module is enabled in the chain configuration
  3. Identify ClawbackVestingAccount addresses
    Query the blockchain for accounts using the ClawbackVestingAccount type, typically via 'evmosd query auth accounts' or blockchain explorer with account type filtering
    Affected if Any ClawbackVestingAccount exists on the network
  4. Review delegation operations from vesting accounts
    Analyze on-chain transactions or use 'evmosd query staking delegations' for each ClawbackVestingAccount address to identify delegation transactions
    Affected if Any delegation transactions exist from a ClawbackVestingAccount
  5. Verify vesting status of delegated tokens
    For each delegation from a vesting account, query the vesting schedule using 'evmosd query vesting clawback-vesting-account' to compare the delegated amount against the vested amount at the time of delegation
    Affected if Delegated token amount exceeds the vested amount at the time of delegation

The environment is affected if running any Evmos version below 18.1.1 with ClawbackVestingAccount enabled and any delegation of unvested tokens has occurred.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 18.1.1 or later which properly validates token vesting status before permitting delegation operations.

Recommended fix Moderate confidence

v18.2.0 or later stable release

  1. 1. Back up your node state and configuration files before upgrading
  2. 2. Check the official Evmos release page on GitHub for the latest stable version after v18.1.0
  3. 3. Stop the Evmos node or validator service
  4. 4. Update the Evmos software to the fixed release (v18.2.0 or later) using your package manager or by compiling from source
  5. 5. Verify the new version is running correctly: `evmosd version`
  6. 6. Ensure the node is synced and functioning properly before re-enabling validator operations
Caveat Review release notes for any consensus changes or migration requirements between v18.1.0 and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Evmos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-37154 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-37154 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data