CVE-2024-32644

Critical

Description

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.

SeverityCritical
CVSS9.1
Exploit probability—
ProductEvmos
PublishedApr 19, 2024
First seenApr 19, 2024
Weakness typeCWE-662CWE-662

How to fix

Update
  • evmos evmos17.0.0 or later
  • github.com/evmos/evmos/v1617.0.0 or later
  • github.com/evmos/evmos/v1717.0.0 or later

Affected products

ProductAffected versionsFixed in
evmos evmosv < 17.0.017.0.0
github.com/evmos/evmos/v16Gov < 17.0.0, No range specified17.0.0
github.com/evmos/evmos/v7Gov ≤ 7.0.0, No range specified—
github.com/evmos/evmos/v6Gov ≤ 6.0.4, No range specified—
github.com/evmos/evmos/v5Gov ≤ 5.0.0, No range specified—
github.com/tharsis/evmosGov ≤ 1.1.3, No range specified—
github.com/tharsis/evmos/v2Gov ≤ 2.0.2, No range specified—
github.com/tharsis/evmos/v3Gov ≤ 3.0.3, No range specified—
github.com/tharsis/evmos/v4Gov ≤ 4.0.2, No range specified—
github.com/tharsis/evmos/v5Gov ≤ 5.0.1, No range specified—
github.com/evmos/evmosGoNo range specified—
github.com/evmos/evmos/v2GoNo range specified—
github.com/evmos/evmos/v3GoNo range specified—
github.com/evmos/evmos/v4GoNo range specified—
github.com/evmos/evmos/v8GoNo range specified—
github.com/evmos/evmos/v9GoNo range specified—
github.com/evmos/evmos/v10GoNo range specified—
github.com/evmos/evmos/v11GoNo range specified—
github.com/evmos/evmos/v12GoNo range specified—
github.com/evmos/evmos/v13GoNo range specified—
github.com/evmos/evmos/v14GoNo range specified—
github.com/evmos/evmos/v15GoNo range specified—
github.com/evmos/evmos/v17Gov < 17.0.017.0.0

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.

CVE-2024-32644 · Evmos · Dark Radar