Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2024-32644: Evmos' transaction execution not accounting for all state transition after interaction with precompiles

Noroxi assessment

Priority: Monitor (action score 36/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.94% (FIRST EPSS); higher than 60.9% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: github.com/evmos/evmos/v16 (Go) 17.0.0; github.com/evmos/evmos/v17 (Go) 17.0.0.

Low priority for now. Upgrade to github.com/evmos/evmos/v16 (Go) 17.0.0; github.com/evmos/evmos/v17 (Go) 17.0.0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Evmos is a scalable, high-throughput Proof-of-Stake EVM blockchain that is fully compatible and interoperable with Ethereum. Prior to 17.0.0, there is a way to mint arbitrary tokens due to the possibility to have two different states not in sync during the execution of a transaction. The exploit is based on the fact that to sync the Cosmos SDK state and the EVM one, we rely on the `stateDB.Commit()` method. When we call this method, we iterate though all the `dirtyStorage` and, **if and only if** it is different than the `originStorage`, we set the new state. Setting the new state means we update the Cosmos SDK KVStore. If a contract storage state that is the same before and after a transaction, but is changed during the transaction and can call an external contract after the change, it can be exploited to make the transaction similar to non-atomic. The vulnerability is **critical** since this could lead to drain of funds through creative SC interactions. The issue has been patched in versions >=V17.0.0.

CriticalCVSS 9.1 · v3.1—No exploit Fix available
Published
Apr 19, 2024
Updated
Jun 17, 2026
EPSS
0.9% · 60th percentile

Report tools

JSON

Action score

36

Monitor

Low priority for now.

CVSS
36 / 40 · 9.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.9%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
9.1
CNA · GitHub_M
9.1
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-32644

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for evmos records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
evmosevmos

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • evmos evmosbefore 17.0.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • evmos evmos

    • < 17.0.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gogithub.com/evmos/evmosfrom 0—
Gogithub.com/evmos/evmos/v10from 0—
Gogithub.com/evmos/evmos/v11from 0—
Gogithub.com/evmos/evmos/v12from 0—
Gogithub.com/evmos/evmos/v13from 0—
Gogithub.com/evmos/evmos/v14from 0—
Gogithub.com/evmos/evmos/v15from 0—
Gogithub.com/evmos/evmos/v16from 0—
Gogithub.com/evmos/evmos/v16before 17.0.017.0.0
Gogithub.com/evmos/evmos/v17before 17.0.017.0.0
Gogithub.com/evmos/evmos/v2from 0—
Gogithub.com/evmos/evmos/v3from 0—
Gogithub.com/evmos/evmos/v4from 0—
Gogithub.com/evmos/evmos/v5from 0—
Gogithub.com/evmos/evmos/v5up to and including 5.0.0—
Gogithub.com/evmos/evmos/v6from 0—
Gogithub.com/evmos/evmos/v6up to and including 6.0.4—
Gogithub.com/evmos/evmos/v7from 0—
Gogithub.com/evmos/evmos/v7up to and including 7.0.0—
Gogithub.com/evmos/evmos/v8from 0—
Gogithub.com/evmos/evmos/v9from 0—
Gogithub.com/tharsis/evmosfrom 0—
Gogithub.com/tharsis/evmosup to and including 1.1.3—
Gogithub.com/tharsis/evmos/v2from 0—

+7

Same product

evmos: all records

Other highest-scoring records for the same primary product.

  • CVE-2024-39696Evmos vulnerable to exploit of smart contract account and vesting
    32Monitor
  • CVE-2024-37158Evmos is missing precompile checks
    32Monitor
  • CVE-2024-37153Evmos's contract balance not updating correctly after interchain transaction
    30Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2022-24738Mar 7, 2022 · Account compromise in Evmos
    29Monitor
  • Later →CVE-2024-32873Jun 6, 2024 · evmos allows transferring unvested tokens after delegations
    17Monitor
  • Later →CVE-2024-37154Jun 6, 2024 · Evmos allows unvested token delegations
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go:github.com/evmos/evmos/v1617.0.0Package registry (OSV)
Go:github.com/evmos/evmos/v1717.0.0Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-662 · Improper Synchronization

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records