Cyber Resilience

CVE-2024-37153

Evmos ≤ 18.1.0

Public PoC
Published
06 June 2024
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 7.5
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:N
EPSS Score 0.0062 46th percentile
Risk Priority 58 floored blend · peak EPSS

Summary

CVE-2024-37153 is a high-severity Always-Incorrect Control Flow Implementation (CWE-670) vulnerability in Evmos Evmos. Its CVSS base score is 7.5 (High).

Operationally, ranked at the 46th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Evmos is the Ethereum Virtual Machine (EVM) Hub on the Cosmos Network. There is an issue with how to liquid stake using Safe which itself is a contract. The bug only appears when there is a local state change together…

more

with an ICS20 transfer in the same function and uses the contract's balance, that is using the contract address as the sender parameter in an ICS20 transfer using the ICS20 precompile. This is in essence the "infinite money glitch" allowing contracts to double the supply of Evmos after each transaction.The issue has been patched in versions >=V18.1.0.

CWE(s)
CWE-670

Related Threats

CVEs Like This One

CVE-2024-39696Same product: Evmos Evmos
CVE-2024-37154Same product: Evmos Evmos
CVE-2024-37159Same product: Evmos Evmos
CVE-2024-37158Same product: Evmos Evmos
CVE-2024-32644Same product: Evmos Evmos
CVE-2024-32873Same product: Evmos Evmos
CVE-2025-32996Shared CWE-670
CVE-2024-25622Shared CWE-670
CVE-2023-41058Shared CWE-670
CVE-2023-52781Shared CWE-670

Affected Assets

evmos
evmos
≤ 18.1.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)
  • V9.2.1

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation at post-design stages directly exercises control-flow paths and reveals mismatches between implemented and intended behavior.

SA-15 Development Process, Standards, and Tools partial match

Requiring a documented development process and supporting tools reduces the chance that incorrect control-flow logic is introduced in the first place.

SI-2 Flaw Remediation partial match

Flaw identification and remediation processes can locate and correct control-flow errors once they manifest as incorrect runtime behavior.

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 prevent incorrect control-flow implementations via reviews, testing, and static analysis.

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 in development and acceptance can detect paths that deviate from intended logic.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle processes can catch incorrect control-flow logic during design and code review.

A.8.28 Secure coding partial match
prevents

Secure coding standards and reviews directly target flawed control-flow implementations.

A.8.32 Change management partial match
prevents

Change-management gates may prevent deployment of flawed logic but do not address the coding defect itself.

References