CVE-2020-16250: Authentication Bypass by Spoofing and Insufficient Verification of Data Authenticity in Hashicorp Vault

CVE-2020-16250 · Severity: low · CVSS 3.1 · Published 2024-08-21

Authentication Bypass by Spoofing and Insufficient Verification of Data Authenticity in Hashicorp Vault in github.com/hashicorp/vault

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

Quick answers

Is CVE-2020-16250 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2020-16250 being exploited in the wild.
How severe is CVE-2020-16250?
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=0.8.1,fixed=1.2.5, SEMVER:introduced=0.8.1,fixed=1.2.5,introduced=1.3.0,fixed=1.3.8,introduced=1.4.0,fixed=1.4.4,introduced=1.5.0,fixed=1.5.1.
Is there a fix for CVE-2020-16250?
Yes. github.com/hashicorp/vault (Go): upgrade to 1.2.5, 1.5.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2020-16250?
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.2.5, 1.5.1 or later
    go get github.com/hashicorp/vault@v1.5.1

Affected products

  • github.com/hashicorp/vault (Go) SEMVER:introduced=0.8.1,fixed=1.2.5, SEMVER:introduced=0.8.1,fixed=1.2.5,introduced=1.3.0,fixed=1.3.8,introduced=1.4.0,fixed=1.4.4,introduced=1.5.0,fixed=1.5.1

Identifiers

  • CVE-2020-16250
  • GHSA-fp52-qw33-mfmw
  • GO-2022-0825

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