CVE-2021-32923 Invalid session token expiration
Attackers can renew nearly-expired leases to bypass expiration checks, maintaining unauthorized access to secrets.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2021-32923?
CVE-2021-32923 is a high-severity vulnerability in Hashicorp Vault, published on 3 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
HashiCorp Vault and Vault Enterprise allowed the renewal of nearly-expired token leases and dynamic secret leases (specifically, those within 1 second of their maximum TTL), which caused them to be incorrectly treated as non-expiring during subsequent use. Fixed in 1.5.9, 1.6.5, and 1.7.2.
Weakness: CWE-613
Which versions are affected by CVE-2021-32923?
8 open source packages ship an affected version, including github.com/hashicorp/vault and vault. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/hashicorp/vault Go | From 0.10.0 | 1.5.9, 1.6.5, 1.7.2 |
github.com/hashicorp/vault Go | From 0.10.0 | 1.5.9 |
github.com/hashicorp/vault Go | From 0.10.0 | 1.5.9 |
github.com/hashicorp/vault Go | From 1.6.0 | 1.6.5 |
github.com/hashicorp/vault Go | From 1.6.0 | 1.6.5 |
github.com/hashicorp/vault Go | From 1.7.0 | 1.7.2 |
2 more packages
github.com/hashicorp/vault Go | From 1.7.0 | 1.7.2 |
vault Bitnami | From 0.10.0 | 1.5.9, 1.6.5, 1.7.2 |
Products include Hashicorp Vault.
How do I fix CVE-2021-32923?
Upgrade github.com/hashicorp/vault to a fixed version for your release line: 1.5.9, 1.6.5 or 1.7.2.
Is CVE-2021-32923 being exploited?
There is no known exploitation of CVE-2021-32923 in the wild and no public exploit code.
Other vulnerabilities in Hashicorp Vault
Sources
Also known as BIT-vault-2021-32923, GHSA-38j9-7pp9-2hjw, GO-2022-0623.