Extended GCP credential access via ignored TTL
Published Jun 10, 2020 · Updated Aug 4, 2024
Incorrect lease handling in HashiCorp Vault 1.4.0 and 1.4.1 allows attackers to retain GCP credentials longer than configured. The service-account-key response path fails to copy the GCP Secrets Engine's configured TTL and maximum TTL into the generated secret, leaving Vault's default lease duration in effect. The flaw requires the GCP Secrets Engine and a key request without an explicit TTL; affected credentials remain usable for GCP actions beyond the configured lease.
Summary
What happened
Incorrect lease handling in HashiCorp Vault 1.4.0 and 1.4.1 allows attackers to retain GCP credentials longer than configured. The service-account-key response path fails to copy the GCP Secrets Engine's configured TTL and maximum TTL into the generated secret, leaving Vault's default lease duration in effect. The flaw requires the GCP Secrets Engine and a key request without an explicit TTL; affected credentials remain usable for GCP actions beyond the configured lease.
The record
- CVE
- CVE-2020-12757
- Published
- Jun 10, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-269, T1078.004
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 10, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo