# CVE-2024-37153: GO-2024-2903 - Contract balance not updating correctly after interchain transaction in github.com/evmos/evmos

Source: https://junglewise.ai/threats/cve-2024-37153-contract-balance-not-updating-correctly-after-interchain  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2024-06-14  
License: CC BY 4.0 with a link back

CVE-2024-37153 · Severity: low · CVSS 3.1 · Published 2024-06-14

Contract balance not updating correctly after interchain transaction in github.com/evmos/evmos

Technologies: [github.com/evmos/evmos (Go)](https://junglewise.ai/threats/technologies/github-com-evmos-evmos), [github.com/evmos/evmos/v10 (Go)](https://junglewise.ai/threats/technologies/github-com-evmos-evmos-v10), [github.com/evmos/evmos/v11 (Go)](https://junglewise.ai/threats/technologies/github-com-evmos-evmos-v11), [github.com/evmos/evmos/v12 (Go)](https://junglewise.ai/threats/technologies/github-com-evmos-evmos-v12), [github.com/evmos/evmos/v13 (Go)](https://junglewise.ai/threats/technologies/github-com-evmos-evmos-v13), [github.com/evmos/evmos/v14 (Go)](https://junglewise.ai/threats/technologies/github-com-evmos-evmos-v14), [github.com/evmos/evmos/v15 (Go)](https://junglewise.ai/threats/technologies/github-com-evmos-evmos-v15), [github.com/evmos/evmos/v16 (Go)](https://junglewise.ai/threats/technologies/github-com-evmos-evmos-v16), [github.com/evmos/evmos/v17 (Go)](https://junglewise.ai/threats/technologies/github-com-evmos-evmos-v17), [github.com/evmos/evmos/v18 (Go)](https://junglewise.ai/threats/technologies/github-com-evmos-evmos-v18), [github.com/evmos/evmos/v2 (Go)](https://junglewise.ai/threats/technologies/github-com-evmos-evmos-v2), [github.com/evmos/evmos/v3 (Go)](https://junglewise.ai/threats/technologies/github-com-evmos-evmos-v3), [github.com/evmos/evmos/v4 (Go)](https://junglewise.ai/threats/technologies/github-com-evmos-evmos-v4), [github.com/evmos/evmos/v5 (Go)](https://junglewise.ai/threats/technologies/github-com-evmos-evmos-v5), [github.com/evmos/evmos/v6 (Go)](https://junglewise.ai/threats/technologies/github-com-evmos-evmos-v6), [github.com/evmos/evmos/v7 (Go)](https://junglewise.ai/threats/technologies/github-com-evmos-evmos-v7), [github.com/evmos/evmos/v8 (Go)](https://junglewise.ai/threats/technologies/github-com-evmos-evmos-v8), [github.com/evmos/evmos/v9 (Go)](https://junglewise.ai/threats/technologies/github-com-evmos-evmos-v9). Vendors: [Go](https://junglewise.ai/threats/vendors/go).

## Quick answers

**Is CVE-2024-37153 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2024-37153 being exploited in the wild.

**How severe is CVE-2024-37153?** Low severity, with a CVSS score of 3.1, published 14 June 2024.

**Which products and versions are affected?** github.com/evmos/evmos (Go) SEMVER:introduced=0; github.com/evmos/evmos/v10 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=18.1.0; github.com/evmos/evmos/v11 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=18.1.0; github.com/evmos/evmos/v12 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=18.1.0; and 14 more.

**Is there a fix for CVE-2024-37153?** Yes. github.com/evmos/evmos/v10 (Go): upgrade to 18.1.0 or later; github.com/evmos/evmos/v11 (Go): upgrade to 18.1.0 or later; github.com/evmos/evmos/v12 (Go): upgrade to 18.1.0 or later; github.com/evmos/evmos/v13 (Go): upgrade to 18.1.0 or later; github.com/evmos/evmos/v14 (Go): upgrade to 18.1.0 or later; github.com/evmos/evmos/v15 (Go): upgrade to 18.1.0 or later; github.com/evmos/evmos/v16 (Go): upgrade to 18.1.0 or later; github.com/evmos/evmos/v17 (Go): upgrade to 18.1.0 or later; github.com/evmos/evmos/v18 (Go): upgrade to 18.1.0 or later; github.com/evmos/evmos/v6 (Go): upgrade to 18.1.0 or later; github.com/evmos/evmos/v7 (Go): upgrade to 18.1.0 or later; github.com/evmos/evmos/v8 (Go): upgrade to 18.1.0 or later; github.com/evmos/evmos/v9 (Go): upgrade to 18.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2024-37153?** Check whether you run github.com/evmos/evmos (Go), github.com/evmos/evmos/v10 (Go), github.com/evmos/evmos/v11 (Go) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/evmos/evmos/v10 (Go): upgrade to 18.1.0 or later

  ```sh
  go get github.com/evmos/evmos/v10@v18.1.0
  ```

- github.com/evmos/evmos/v11 (Go): upgrade to 18.1.0 or later

  ```sh
  go get github.com/evmos/evmos/v11@v18.1.0
  ```

- github.com/evmos/evmos/v12 (Go): upgrade to 18.1.0 or later

  ```sh
  go get github.com/evmos/evmos/v12@v18.1.0
  ```

- github.com/evmos/evmos/v13 (Go): upgrade to 18.1.0 or later

  ```sh
  go get github.com/evmos/evmos/v13@v18.1.0
  ```

- github.com/evmos/evmos/v14 (Go): upgrade to 18.1.0 or later

  ```sh
  go get github.com/evmos/evmos/v14@v18.1.0
  ```

- github.com/evmos/evmos/v15 (Go): upgrade to 18.1.0 or later

  ```sh
  go get github.com/evmos/evmos/v15@v18.1.0
  ```

- github.com/evmos/evmos/v16 (Go): upgrade to 18.1.0 or later

  ```sh
  go get github.com/evmos/evmos/v16@v18.1.0
  ```

- github.com/evmos/evmos/v17 (Go): upgrade to 18.1.0 or later

  ```sh
  go get github.com/evmos/evmos/v17@v18.1.0
  ```

- github.com/evmos/evmos/v18 (Go): upgrade to 18.1.0 or later

  ```sh
  go get github.com/evmos/evmos/v18@v18.1.0
  ```

- github.com/evmos/evmos/v6 (Go): upgrade to 18.1.0 or later

  ```sh
  go get github.com/evmos/evmos/v6@v18.1.0
  ```

- github.com/evmos/evmos/v7 (Go): upgrade to 18.1.0 or later

  ```sh
  go get github.com/evmos/evmos/v7@v18.1.0
  ```

- github.com/evmos/evmos/v8 (Go): upgrade to 18.1.0 or later

  ```sh
  go get github.com/evmos/evmos/v8@v18.1.0
  ```

- github.com/evmos/evmos/v9 (Go): upgrade to 18.1.0 or later

  ```sh
  go get github.com/evmos/evmos/v9@v18.1.0
  ```


## Affected products

- github.com/evmos/evmos (Go) SEMVER:introduced=0
- github.com/evmos/evmos/v10 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=18.1.0
- github.com/evmos/evmos/v11 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=18.1.0
- github.com/evmos/evmos/v12 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=18.1.0
- github.com/evmos/evmos/v13 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=18.1.0
- github.com/evmos/evmos/v14 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=18.1.0
- github.com/evmos/evmos/v15 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=18.1.0
- github.com/evmos/evmos/v16 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=18.1.0
- github.com/evmos/evmos/v17 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=18.1.0
- github.com/evmos/evmos/v18 (Go) SEMVER:introduced=0,fixed=18.1.0
- github.com/evmos/evmos/v2 (Go) SEMVER:introduced=0
- github.com/evmos/evmos/v3 (Go) SEMVER:introduced=0
- github.com/evmos/evmos/v4 (Go) SEMVER:introduced=0
- github.com/evmos/evmos/v5 (Go) SEMVER:introduced=0
- github.com/evmos/evmos/v6 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=18.1.0
- github.com/evmos/evmos/v7 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=18.1.0
- github.com/evmos/evmos/v8 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=18.1.0
- github.com/evmos/evmos/v9 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=18.1.0

## Identifiers

- CVE-2024-37153
- GHSA-xgr7-jgq3-mhmc
- GO-2024-2903

## Related threats

- [GO-2022-0760 - Ethermint vulnerable to DoS through unintended Contract Selfdestruct in github.com/crypto-org-chain/cronos](https://junglewise.ai/threats/cve-2022-35936-ethermint-vulnerable-to-dos-through-unintended-contract)
- [GO-2024-2974 - Evmos vulnerable to exploit of smart contract account and vesting in github.com/evmos/evmos](https://junglewise.ai/threats/cve-2024-39696-evmos-vulnerable-to-exploit-of-smart-contract-account-and-vesting)
- [GO-2024-2927 - Evmos is missing create validator check in github.com/evmos/evmos](https://junglewise.ai/threats/cve-2024-32873-evmos-allows-transferring-unvested-tokens-after-delegations)
- [GO-2024-2904 - Evmos allows unvested token delegations in github.com/evmos/evmos](https://junglewise.ai/threats/cve-2024-37154-evmos-allows-unvested-token-delegations)
- [GO-2024-2731 - Evmos vulnerable to unauthorized account creation with vesting module in github.com/evmos/evmos](https://junglewise.ai/threats/go-2024-2731-evmos-vulnerable-to-unauthorized-account-creation-with-70388618)