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

CVE-2024-32644 · Severity: low · CVSS 3.1 · Published 2024-06-05

Evmos transaction execution not accounting for all state transition after interaction with precompiles in github.com/evmos/evmos

Technologies: github.com/evmos/evmos (Go), github.com/evmos/evmos/v10 (Go), github.com/evmos/evmos/v11 (Go), github.com/evmos/evmos/v12 (Go), github.com/evmos/evmos/v13 (Go), github.com/evmos/evmos/v14 (Go), github.com/evmos/evmos/v15 (Go), github.com/evmos/evmos/v16 (Go), github.com/evmos/evmos/v17 (Go), github.com/evmos/evmos/v2 (Go), github.com/evmos/evmos/v3 (Go), github.com/evmos/evmos/v4 (Go), github.com/evmos/evmos/v5 (Go), github.com/evmos/evmos/v6 (Go), github.com/evmos/evmos/v7 (Go), github.com/evmos/evmos/v8 (Go), github.com/evmos/evmos/v9 (Go), github.com/tharsis/evmos (Go). Vendors: Go.

Quick answers

Is CVE-2024-32644 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2024-32644 being exploited in the wild.
How severe is CVE-2024-32644?
Low severity, with a CVSS score of 3.1, published 5 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; github.com/evmos/evmos/v11 (Go) SEMVER:introduced=0; github.com/evmos/evmos/v12 (Go) SEMVER:introduced=0; and 18 more.
Is there a fix for CVE-2024-32644?
Yes. github.com/evmos/evmos/v16 (Go): upgrade to 17.0.0 or later; github.com/evmos/evmos/v17 (Go): upgrade to 17.0.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-32644?
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/v16 (Go): upgrade to 17.0.0 or later
    go get github.com/evmos/evmos/v16@v17.0.0
  • github.com/evmos/evmos/v17 (Go): upgrade to 17.0.0 or later
    go get github.com/evmos/evmos/v17@v17.0.0

Affected products

  • github.com/evmos/evmos (Go) SEMVER:introduced=0
  • github.com/evmos/evmos/v10 (Go) SEMVER:introduced=0
  • github.com/evmos/evmos/v11 (Go) SEMVER:introduced=0
  • github.com/evmos/evmos/v12 (Go) SEMVER:introduced=0
  • github.com/evmos/evmos/v13 (Go) SEMVER:introduced=0
  • github.com/evmos/evmos/v14 (Go) SEMVER:introduced=0
  • github.com/evmos/evmos/v15 (Go) SEMVER:introduced=0
  • github.com/evmos/evmos/v16 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=17.0.0
  • github.com/evmos/evmos/v17 (Go) SEMVER:introduced=0,fixed=17.0.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, SEMVER:introduced=0,last_affected=5.0.0
  • github.com/evmos/evmos/v6 (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=6.0.4
  • github.com/evmos/evmos/v7 (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=7.0.0
  • github.com/evmos/evmos/v8 (Go) SEMVER:introduced=0
  • github.com/evmos/evmos/v9 (Go) SEMVER:introduced=0
  • github.com/tharsis/evmos (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.1.3
  • github.com/tharsis/evmos/v2 (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=2.0.2
  • github.com/tharsis/evmos/v3 (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=3.0.3
  • github.com/tharsis/evmos/v4 (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=4.0.2
  • github.com/tharsis/evmos/v5 (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=5.0.1

Identifiers

  • CVE-2024-32644
  • GHSA-3fp5-2xwh-fxm6
  • GO-2024-2715

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.