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

> Attackers can obtain GCP credentials with longer validity than intended when using the GCP Secrets Engine, potentially extending access windows.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** BIT-vault-2020-12757, GHSA-75pc-qvwc-jf3g, GO-2022-0804

## What is CVE-2020-12757?

CVE-2020-12757 is a critical vulnerability in Hashicorp Vault, published on 10 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HashiCorp Vault and Vault Enterprise 1.4.0 and 1.4.1, when configured with the GCP Secrets Engine, may incorrectly generate GCP Credentials with the default time-to-live lease duration instead of the engine-configured setting. This may lead to generated GCP credentials being valid for longer than intended. Fixed in 1.4.2.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2020-12757?

4 open source packages ship an affected version, including github.com/hashicorp/vault-plugin-secrets-gcp and vault. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/hashicorp/vault-plugin-secrets-gcp` | Go | All versions | 0.6.2 |
| `github.com/hashicorp/vault-plugin-secrets-gcp` | Go | All versions | 0.6.2 |
| `github.com/hashicorp/vault-plugin-secrets-gcp` | Go | All versions | 0.6.2 |
| `vault` | Bitnami | From 1.4.0 | 1.4.2 |

Products: Hashicorp Vault.

## How do I fix CVE-2020-12757?

Upgrade github.com/hashicorp/vault-plugin-secrets-gcp to 0.6.2 or later.

## Is CVE-2020-12757 being exploited?

There is no known exploitation of CVE-2020-12757 in the wild and no public exploit code.

## Other vulnerabilities in Hashicorp Vault

- [CVE-2020-35192](https://insights.sbomify.com/CVE-2020-35192/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2025-6000](https://insights.sbomify.com/CVE-2025-6000/): Arbitrary Remote Code Execution via Plugin Catalog Abuse (critical 9.1)
- [CVE-2022-40186](https://insights.sbomify.com/CVE-2022-40186/): HashiCorp Vault vulnerable to incorrect metadata access (critical 9.1)
- [CVE-2022-36129](https://insights.sbomify.com/CVE-2022-36129/): Missing authorization in n/a (critical 9.1)
- [CVE-2020-10661](https://insights.sbomify.com/CVE-2020-10661/): HashiCorp Vault Improper Privilege Management (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-12757 and fix it if it is affected.

What it is: CVE-2020-12757 is a critical vulnerability in Hashicorp Vault, published on 10 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-12757 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/hashicorp/vault-plugin-secrets-gcp (Go): affected all versions; fixed in 0.6.2
- github.com/hashicorp/vault-plugin-secrets-gcp (Go): affected all versions; fixed in 0.6.2
- github.com/hashicorp/vault-plugin-secrets-gcp (Go): affected all versions; fixed in 0.6.2
- vault (Bitnami): affected from 1.4.0; fixed in 1.4.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-12757/ (Markdown: https://insights.sbomify.com/CVE-2020-12757/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-12757
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-12757
- OSV: https://osv.dev/vulnerability/CVE-2020-12757

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-12757/
Summaries are generated and may contain mistakes; the official description above is the record.