CVE-2020-12757: Improper Input Validation in HashiCorp Vault

Summary

18/05/2021
Yes i
Critical
9.8

CVE-2020-12757: Improper Input Validation in HashiCorp Vault. Affects github.com/hashicorp/vault-plugin-secrets-gcp versions < 0.6.2. Fixed in 0.6.2. How to fix ↓

Also tracked for

The same CVE-2020-12757 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

HashiCorp Vault is a popular open-source tool used for securely storing and accessing secrets. It provides a centralized solution for managing sensitive information such as API keys, passwords, and certificates. The vulnerability identified as CVE-2020-12757 affects HashiCorp Vault and Vault Enterprise versions 1.4.x before 1.4.2. This vulnerability is categorized as a high-severity issue and is related to incorrect access control.

Vulnerability Detail

The vulnerability in HashiCorp Vault allows for improper input validation, which can lead to unauthorized access to sensitive data. Attackers can exploit this vulnerability to bypass access controls and gain unauthorized privileges within the system. This can result in the exposure of confidential information, compromise of secrets, and potential unauthorized actions within the Vault environment. The vulnerability has a CVSS score of 4.0, indicating a moderate level of severity.

How To Fix

Minimum fixed version

0.6.2

This is the first release that contains the fix.

go get github.com/hashicorp/vault-plugin-secrets-gcp@v0.6.2

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. The recommended approach is to upgrade to the patched version of HashiCorp Vault.

Conclusion

The vulnerability identified as CVE-2020-12757 in HashiCorp Vault is a high-severity issue that allows for improper input validation. Upgrading to HashiCorp Vault and Vault Enterprise version 1.4.2 or later is the recommended solution to mitigate this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for github.com/hashicorp/vault-plugin-secrets-gcp →

Share this vulnerability

FAQ

HashiCorp Vault is an open-source tool used for securely storing and accessing secrets. It provides a centralized solution for managing sensitive information such as API keys, passwords, and certificates.

The vulnerability allows for improper input validation, which can lead to unauthorized access to sensitive data. Attackers can exploit this vulnerability to bypass access controls and gain unauthorized privileges within the system, potentially exposing confidential information and compromising secrets.

The CVSS score of this vulnerability is 4.0, indicating a moderate level of severity.

To fix this vulnerability, it is recommended to upgrade to HashiCorp Vault and Vault Enterprise version 1.4.2 or later. This version includes the necessary patches and security enhancements to mitigate the vulnerability.

There is no specific workaround mentioned for this vulnerability. The recommended approach is to upgrade to the patched version of HashiCorp Vault.

How To Fix

Minimum fixed version

0.6.2

This is the first release that contains the fix.

go get github.com/hashicorp/vault-plugin-secrets-gcp@v0.6.2

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback