CVE-2020-13223: Information Disclosure in HashiCorp Vault
Summary
CVE-2020-13223: Information Disclosure in HashiCorp Vault. Affects github.com/hashicorp/vault across 2 version ranges.
>= 1.3.0, < 1.3.6
>= 1.4.0, < 1.4.2
Fixed in 1.3.6 or 1.4.2, depending on the release line you run. How to fix ↓
Also tracked for
- vault · Bitnami
The same CVE-2020-13223 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
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.
No signup required · Results in about 60 seconds
Background
HashiCorp Vault is a popular open-source tool used for securely storing and accessing sensitive information such as passwords, API keys, and encryption keys. It provides a centralized solution for managing secrets and access control. The affected package, github.com/hashicorp/vault/command, is a Go package that includes the command-line interface (CLI) for interacting with HashiCorp Vault. This vulnerability allows sensitive information to be logged, potentially exposing it to unauthorized access.
Vulnerability Detail
The vulnerability, identified as CVE-2020-13223, occurs in versions of HashiCorp Vault and Vault Enterprise prior to 1.3.6 and 1.4.2, respectively. When executing certain commands, sensitive information is unintentionally written to a log file. This can include secrets, access tokens, or other confidential data. An attacker with access to the log file may be able to extract this information and abuse it for unauthorized access or other malicious purposes. The vulnerability has a CVSS score of 7.5, indicating a high severity level.
How To Fix
Latest published version: v1.21.4 as of 23 Oct 2026
go get github.com/hashicorp/vault@v1.21.4Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
>= 1.3.0, < 1.3.61.3.6go get github.com/hashicorp/vault@v1.3.6 -
>= 1.4.0, < 1.4.21.4.2go get github.com/hashicorp/vault@v1.4.2
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
There is no specific workaround provided for this vulnerability. Upgrading to the patched versions is the recommended solution.
Conclusion
The vulnerability in HashiCorp Vault allows sensitive information to be logged, potentially exposing it to unauthorized access. To mitigate this risk, it is crucial to upgrade to the patched versions of HashiCorp Vault (1.3.6 or later for Vault, and 1.4.2 or later for Vault Enterprise). Additionally, proper security measures should be implemented to protect log files and restrict access to authorized personnel only. For further assistance or support in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for github.com/hashicorp/vault →
FAQ
HashiCorp Vault is an open-source tool used for securely storing and accessing sensitive information.
This vulnerability can lead to the exposure of sensitive information, potentially enabling unauthorized access or misuse of confidential data.
You can use the Vulert Playground at Vulert Scanner to check if your version of HashiCorp Vault is affected by this vulnerability. No signup is required.
There are no known exploits for this vulnerability at the time of this report. However, it is important to apply the necessary patches to mitigate the risk.
You can find more information about this vulnerability in the GitHub Advisory Database at the following link: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2021/05/GHSA-25xj-89g5-fm6h/GHSA-25xj-89g5-fm6h.json
References
Related vulnerabilities
Recent vulnerabilities recorded for github.com/hashicorp/vault.
