Skip to content
Fencer Vulns
critical 9.1

CVE-2024-32644 json

Evmos' transaction execution not accounting for all state transition after interaction with precompiles

published 2024-04-10 2 y ago modified 2026-09-10 1 mo ago also EUVD-2024-1080 , GHSA-3fp5-2xwh-fxm6 , GO-2024-2715

cvss
9.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 61%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/evmos/evmos/v16 17.0.0
  • go github.com/evmos/evmos/v17 17.0.0
  • evmos evmos 17.0.0

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
2 y ago

Exploit prediction

0.94% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
GitHub 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
NVD 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Affected packages

ecosystem package affected fixed in
go github.com/evmos/evmos/v16
<17.0.0
all versions
17.0.0
go github.com/evmos/evmos/v7
<=7.0.0
all versions
 no fix listed
go github.com/evmos/evmos/v6
<=6.0.4
all versions
 no fix listed
go github.com/evmos/evmos/v5
<=5.0.0
all versions
 no fix listed
go github.com/tharsis/evmos
<=1.1.3
all versions
 no fix listed
go github.com/tharsis/evmos/v2
<=2.0.2
all versions
 no fix listed
go github.com/tharsis/evmos/v3
<=3.0.3
all versions
 no fix listed
go github.com/tharsis/evmos/v4
<=4.0.2
all versions
 no fix listed
go github.com/tharsis/evmos/v5
<=5.0.1
all versions
 no fix listed
go github.com/evmos/evmos
all versions
 no fix listed
go github.com/evmos/evmos/v2
all versions
 no fix listed
go github.com/evmos/evmos/v3
all versions
 no fix listed
go github.com/evmos/evmos/v4
all versions
 no fix listed
go github.com/evmos/evmos/v8
all versions
 no fix listed
go github.com/evmos/evmos/v9
all versions
 no fix listed
go github.com/evmos/evmos/v10
all versions
 no fix listed
go github.com/evmos/evmos/v11
all versions
 no fix listed
go github.com/evmos/evmos/v12
all versions
 no fix listed
go github.com/evmos/evmos/v13
all versions
 no fix listed
go github.com/evmos/evmos/v14
all versions
 no fix listed
go github.com/evmos/evmos/v15
all versions
 no fix listed
go github.com/evmos/evmos/v17
<17.0.0
17.0.0

Affected products

  • evmos evmos

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.