CVE-2024-8185: GO-2024-3246 - Hashicorp Vault vulnerable to denial of service through memory exhaustion in github.com/hashicorp/vault

CVE-2024-8185 · Severity: low · CVSS 3.1 · Published 2024-11-01

Hashicorp Vault vulnerable to denial of service through memory exhaustion in github.com/hashicorp/vault

Technologies: github.com/hashicorp/vault (Go), github.com/openbao/openbao (Go). Vendors: Go.

Quick answers

Is CVE-2024-8185 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2024-8185 being exploited in the wild.
How severe is CVE-2024-8185?
Low severity, with a CVSS score of 3.1, published 1 November 2024.
Which products and versions are affected?
github.com/hashicorp/vault (Go) SEMVER:introduced=1.2.0,fixed=1.18.1; github.com/openbao/openbao (Go) SEMVER:introduced=0,fixed=2.0.3.
Is there a fix for CVE-2024-8185?
Yes. github.com/hashicorp/vault (Go): upgrade to 1.18.1 or later; github.com/openbao/openbao (Go): upgrade to 2.0.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2024-8185?
Check whether you run github.com/hashicorp/vault (Go) or github.com/openbao/openbao (Go) 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/hashicorp/vault (Go): upgrade to 1.18.1 or later
    go get github.com/hashicorp/vault@v1.18.1
  • github.com/openbao/openbao (Go): upgrade to 2.0.3 or later
    go get github.com/openbao/openbao@v2.0.3

Affected products

  • github.com/hashicorp/vault (Go) SEMVER:introduced=1.2.0,fixed=1.18.1
  • github.com/openbao/openbao (Go) SEMVER:introduced=0,fixed=2.0.3

Identifiers

  • CVE-2024-8185
  • GHSA-g233-2p4r-3q7v
  • GO-2024-3246

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