CVE-2022-40186: GO-2022-1021 - HashiCorp Vault vulnerable to incorrect metadata access in github.com/hashicorp/vault

CVE-2022-40186 · Severity: low · CVSS 3.1 · Published 2024-08-21

HashiCorp Vault vulnerable to incorrect metadata access in github.com/hashicorp/vault

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

Quick answers

Is CVE-2022-40186 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2022-40186 being exploited in the wild.
How severe is CVE-2022-40186?
Low severity, with a CVSS score of 3.1, published 21 August 2024.
Which products and versions are affected?
github.com/hashicorp/vault (Go) SEMVER:introduced=1.11.0,fixed=1.11.3, SEMVER:introduced=1.8.0,fixed=1.9.9,introduced=1.10.0,fixed=1.10.6,introduced=1.11.0,fixed=1.11.3.
Is there a fix for CVE-2022-40186?
Yes. github.com/hashicorp/vault (Go): upgrade to 1.11.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-40186?
Check whether you run github.com/hashicorp/vault (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.11.3 or later
    go get github.com/hashicorp/vault@v1.11.3

Affected products

  • github.com/hashicorp/vault (Go) SEMVER:introduced=1.11.0,fixed=1.11.3, SEMVER:introduced=1.8.0,fixed=1.9.9,introduced=1.10.0,fixed=1.10.6,introduced=1.11.0,fixed=1.11.3

Identifiers

  • CVE-2022-40186
  • GHSA-7cgv-v83v-rr87
  • GO-2022-1021

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