CVE-2022-41316 HashiCorp Vault's revocation list not respected
Attackers can bypass certificate revocation checks in HashiCorp Vault if CRLs are not loaded at startup, allowing revoked certificates to remain valid.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2022-41316?
CVE-2022-41316 is a medium-severity vulnerability in Hashicorp Vault, published on 12 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
HashiCorp Vault and Vault Enterprise’s TLS certificate auth method did not initially load the optionally configured CRL issued by the role's CA into memory on startup, resulting in the revocation list not being checked if the CRL has not yet been retrieved. Fixed in 1.12.0, 1.11.4, 1.10.7, and 1.9.10.
Weakness: CWE-295
Which versions are affected by CVE-2022-41316?
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 | All versions | 1.9.10, 1.10.7, 1.11.4 |
github.com/hashicorp/vault Go | All versions | 1.9.10 |
github.com/hashicorp/vault Go | All versions | 1.9.10 |
github.com/hashicorp/vault Go | From 1.10.0 | 1.10.7 |
github.com/hashicorp/vault Go | From 1.10.0 | 1.10.7 |
github.com/hashicorp/vault Go | From 1.11.0 | 1.11.4 |
2 more packages
github.com/hashicorp/vault Go | From 1.11.0 | 1.11.4 |
vault Bitnami | All versions | 1.9.10, 1.10.7, 1.11.4 |
Products include Hashicorp Vault.
How do I fix CVE-2022-41316?
Upgrade github.com/hashicorp/vault to a fixed version for your release line: 1.9.10, 1.10.7 or 1.11.4.
Is CVE-2022-41316 being exploited?
There is no known exploitation of CVE-2022-41316 in the wild and no public exploit code.
Other vulnerabilities in Hashicorp Vault
Sources
Also known as BIT-vault-2022-41316, GHSA-9mh8-9j64-443f, GO-2023-1897.