---
title: "CVE-2024-32644: Evmos transaction execution not accounting for all state transition after interaction with precompiles"
url: https://erroneo.us/security/cve/CVE-2024-32644/
description: "CVE-2024-32644 (github.com/evmos/evmos/v16 (Go)): Evmos is a scalable, high-throughput Proof-of-Stake EVM blockchain that is fully compatible and…"
type: vulnerability-record
section: "Security Digest"
date_published: 2024-04-19
date_modified: 2024-08-02
publisher: erroneo.us
author: erroneo.us Security Desk
cve: "CVE-2024-32644"
kev: false
cvss: 9.1
epss: 0.00943
license: All rights reserved. Quote with attribution and a link.
---

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

**Signal:** Critical and remotely reachable. No known exploitation yet, but it is network-reachable without credentials. (Computed from CISA KEV, EPSS and CVSS; not an editorial verdict.)

## Should you act?

- No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
- EPSS 0.9% , percentile 61: FIRST’s model estimates a 0.9% chance of exploitation activity in the next 30 days, higher than 61% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes github.com/evmos/evmos/v16 (Go) <= 16.0.4, fixed in 17.0.0 ; github.com/evmos/evmos/v7 (Go) <= 7.0.0, no fixed version listed ; github.com/evmos/evmos/v6 (Go) <= 6.0.4, no fixed version listed ; github.com/evmos/evmos/v5 (Go) <= 5.0.0, no fixed version listed . Check your lockfile, including transitive dependencies.

## What it is

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.

## Affected packages

- Go `github.com/evmos/evmos/v16` <= 16.0.4 → fixed: 17.0.0
- Go `github.com/evmos/evmos/v7` <= 7.0.0 → fixed: none listed
- Go `github.com/evmos/evmos/v6` <= 6.0.4 → fixed: none listed
- Go `github.com/evmos/evmos/v5` <= 5.0.0 → fixed: none listed
- Go `github.com/tharsis/evmos` <= 1.1.3 → fixed: none listed
- Go `github.com/tharsis/evmos/v2` <= 2.0.2 → fixed: none listed
- Go `github.com/tharsis/evmos/v3` <= 3.0.3 → fixed: none listed
- Go `github.com/tharsis/evmos/v4` <= 4.0.2 → fixed: none listed
- Go `github.com/tharsis/evmos/v5` <= 5.0.1 → fixed: none listed

## Affected products (CVE record)

- evmos evmos: < 17.0.0

## Severity

- GitHub_M CVSS 3.1: 9.1 `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`
- GitHub CVSS 3.1: 9.1 `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`

## Exploitation

- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation none , automatable yes , technical impact total .
- FIRST EPSS (model of 2026-10-21): 0.94% probability of exploitation activity in the next 30 days; percentile 61.

## Sources

- [GitHub Advisory GHSA-3fp5-2xwh-fxm6](https://github.com/advisories/GHSA-3fp5-2xwh-fxm6)
- [CVE.org record CVE-2024-32644](https://www.cve.org/CVERecord?id=CVE-2024-32644)
- [NVD entry CVE-2024-32644](https://nvd.nist.gov/vuln/detail/CVE-2024-32644)
- [github.com](https://github.com/evmos/evmos/security/advisories/GHSA-3fp5-2xwh-fxm6)
- [github.com](https://github.com/evmos/evmos/commit/08982b5ee726b97bc50eaf58d1914829648b6a5f)
- [github.com](https://github.com/evmos/evmos/blob/b196a522ba4951890b40992e9f97aa610f8b5f9c/x/evm/statedb/statedb.go#L460-L465)
- [github.com](https://github.com/evmos/evmos/blob/b196a522ba4951890b40992e9f97aa610f8b5f9c/x/evm/statedb/state_object.go#L53-L68)
- [github.com](https://github.com/evmos/evmos/blob/b196a522ba4951890b40992e9f97aa610f8b5f9c/x/evm/statedb/statedb.go#L33-L55)

---
Source page: https://erroneo.us/security/cve/CVE-2024-32644/ · Security Digest: https://erroneo.us/security/ · More: https://erroneo.us/llms.txt