CVE-2024-37159: GO-2024-2927 - Evmos is missing create validator check in github.com/evmos/evmos

CVE-2024-37159 · Severity: low · CVSS 3.1 · Published 2024-06-28

Evmos is missing create validator check 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/v18 (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). Vendors: Go.

Quick answers

Is CVE-2024-37159 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2024-37159 being exploited in the wild.
How severe is CVE-2024-37159?
Low severity, with a CVSS score of 3.1, published 28 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.0.0; github.com/evmos/evmos/v11 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=18.0.0; github.com/evmos/evmos/v12 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=18.0.0; and 14 more.
Is there a fix for CVE-2024-37159?
Yes. github.com/evmos/evmos/v10 (Go): upgrade to 18.0.0 or later; github.com/evmos/evmos/v11 (Go): upgrade to 18.0.0 or later; github.com/evmos/evmos/v12 (Go): upgrade to 18.0.0 or later; github.com/evmos/evmos/v13 (Go): upgrade to 18.0.0 or later; github.com/evmos/evmos/v14 (Go): upgrade to 18.0.0 or later; github.com/evmos/evmos/v15 (Go): upgrade to 18.0.0 or later; github.com/evmos/evmos/v16 (Go): upgrade to 18.0.0 or later; github.com/evmos/evmos/v17 (Go): upgrade to 18.0.0 or later; github.com/evmos/evmos/v18 (Go): upgrade to 18.0.0 or later; github.com/evmos/evmos/v6 (Go): upgrade to 18.0.0 or later; github.com/evmos/evmos/v7 (Go): upgrade to 18.0.0 or later; github.com/evmos/evmos/v8 (Go): upgrade to 18.0.0 or later; github.com/evmos/evmos/v9 (Go): upgrade to 18.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-37159?
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.0.0 or later
    go get github.com/evmos/evmos/v10@v18.0.0
  • github.com/evmos/evmos/v11 (Go): upgrade to 18.0.0 or later
    go get github.com/evmos/evmos/v11@v18.0.0
  • github.com/evmos/evmos/v12 (Go): upgrade to 18.0.0 or later
    go get github.com/evmos/evmos/v12@v18.0.0
  • github.com/evmos/evmos/v13 (Go): upgrade to 18.0.0 or later
    go get github.com/evmos/evmos/v13@v18.0.0
  • github.com/evmos/evmos/v14 (Go): upgrade to 18.0.0 or later
    go get github.com/evmos/evmos/v14@v18.0.0
  • github.com/evmos/evmos/v15 (Go): upgrade to 18.0.0 or later
    go get github.com/evmos/evmos/v15@v18.0.0
  • github.com/evmos/evmos/v16 (Go): upgrade to 18.0.0 or later
    go get github.com/evmos/evmos/v16@v18.0.0
  • github.com/evmos/evmos/v17 (Go): upgrade to 18.0.0 or later
    go get github.com/evmos/evmos/v17@v18.0.0
  • github.com/evmos/evmos/v18 (Go): upgrade to 18.0.0 or later
    go get github.com/evmos/evmos/v18@v18.0.0
  • github.com/evmos/evmos/v6 (Go): upgrade to 18.0.0 or later
    go get github.com/evmos/evmos/v6@v18.0.0
  • github.com/evmos/evmos/v7 (Go): upgrade to 18.0.0 or later
    go get github.com/evmos/evmos/v7@v18.0.0
  • github.com/evmos/evmos/v8 (Go): upgrade to 18.0.0 or later
    go get github.com/evmos/evmos/v8@v18.0.0
  • github.com/evmos/evmos/v9 (Go): upgrade to 18.0.0 or later
    go get github.com/evmos/evmos/v9@v18.0.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.0.0
  • github.com/evmos/evmos/v11 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=18.0.0
  • github.com/evmos/evmos/v12 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=18.0.0
  • github.com/evmos/evmos/v13 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=18.0.0
  • github.com/evmos/evmos/v14 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=18.0.0
  • github.com/evmos/evmos/v15 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=18.0.0
  • github.com/evmos/evmos/v16 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=18.0.0
  • github.com/evmos/evmos/v17 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=18.0.0
  • github.com/evmos/evmos/v18 (Go) SEMVER:introduced=0,fixed=18.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
  • github.com/evmos/evmos/v6 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=18.0.0
  • github.com/evmos/evmos/v7 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=18.0.0
  • github.com/evmos/evmos/v8 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=18.0.0
  • github.com/evmos/evmos/v9 (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=18.0.0

Identifiers

  • CVE-2024-37159
  • CVE-2024-37158
  • CVE-2024-32873
  • GHSA-pxv8-qhrh-jc7v
  • GO-2024-2891
  • GO-2024-2926
  • GO-2024-2927

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