CVE-2024-32644Network attack vector

Arbitrary token minting via stale state commit

Published Apr 19, 2024 · Updated Aug 2, 2024

Improper synchronization in Evmos before 17.0.0 allows remote attackers to mint arbitrary tokens through crafted smart-contract transactions. During a precompile call, stateDB.Commit() writes dirtyStorage to the Cosmos SDK KVStore without updating originStorage, so the final commit skips a restored value that compares equal to stale originStorage. An unauthenticated attacker must submit a contract transaction that changes storage, calls an external precompile, and restores the original value; the resulting non-atomic state can drain funds.

CVSS severity9.1
Critical
EPSS probability0.94%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper synchronization in Evmos before 17.0.0 allows remote attackers to mint arbitrary tokens through crafted smart-contract transactions. During a precompile call, stateDB.Commit() writes dirtyStorage to the Cosmos SDK KVStore without updating originStorage, so the final commit skips a restored value that compares equal to stale originStorage. An unauthenticated attacker must submit a contract transaction that changes storage, calls an external precompile, and restores the original value; the resulting non-atomic state can drain funds.

The record

CVE
CVE-2024-32644
Published
Apr 19, 2024
Updated
Aug 2, 2024
Vendor
Evmos
Product
Evmos
Classifications
CWE-662, T1657
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Apr 19, 2024CVE publishedPublication date reported by the CVE source.
  2. Aug 2, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 17.0.0
  2. Affected versionversion=17.0.0* <17.0.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Evmos · Evmosversion=< 17.0.0; version=17.0.0* <17.0.0

Published CVSS scores

9.1GitHubCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
9.1NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-662Improper Synchronization
T1657Financial Theft

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo