Cyber Resilience

CVE-2024-32644

Evmos ≤ 17.0.0

Published
19 April 2024
Modified
06 March 2025
Patch / advisory
View advisory
CVSS Score v3.1 9.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
EPSS Score 0.0094 58th percentile
Risk Priority 69 floored blend · peak EPSS

Summary

CVE-2024-32644 is a critical-severity Improper Synchronization (CWE-662) vulnerability in Evmos Evmos. Its CVSS base score is 9.1 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 42% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-39 (Process Isolation) and SC-4 (Information in Shared System Resources) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
CWE-662NVD-CWE-noinfo

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
attack.mitre.org →
T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-39696Same product: Evmos Evmos
CVE-2024-32873Same product: Evmos Evmos
CVE-2024-37159Same product: Evmos Evmos
CVE-2024-37154Same product: Evmos Evmos
CVE-2024-37153Same product: Evmos Evmos
CVE-2024-37158Same product: Evmos Evmos
CVE-2024-7409Shared CWE-662
CVE-2025-27104Shared CWE-662
CVE-2025-22853Shared CWE-662
CVE-2023-5088Shared CWE-662

Affected Assets

evmos
evmos
≤ 17.0.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V15.4.1
  • V6.5.1
  • V15.1.3
  • V15.4.2

Mitigating Controls (NIST 800-53 r5) AI

SC-39 Process Isolation partial match

Process isolation reduces the attack surface and blast radius of synchronization failures but does not itself implement the required synchronization.

SC-4 Information in Shared System Resources partial match

SC-4 directly requires preventing unintended information transfer through shared resources, which is achieved only by proper synchronization primitives for exclusive access.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require synchronization mechanisms and concurrency testing to prevent race conditions.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect synchronization flaws but does not itself implement the required controls.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle requires concurrency controls and synchronization primitives to prevent race conditions.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture principles include thread-safety and resource-locking mechanisms to avoid improper synchronization.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly mandate proper use of locks, semaphores, and atomic operations to eliminate race conditions.

References