Vulnerability 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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Hashicorp | Vault | < 1.9.10 |
Related Weaknesses (CWE)
References
- https://discuss.hashicorp.comVendor Advisory
- https://discuss.hashicorp.com/t/hcsec-2022-24-vaults-tls-cert-auth-method-only-lVendor Advisory
- https://security.netapp.com/advisory/ntap-20221201-0001/Third Party Advisory
- https://discuss.hashicorp.comVendor Advisory
- https://discuss.hashicorp.com/t/hcsec-2022-24-vaults-tls-cert-auth-method-only-lVendor Advisory
- https://security.netapp.com/advisory/ntap-20221201-0001/Third Party Advisory
FAQ
What is CVE-2022-41316?
CVE-2022-41316 is a vulnerability with a CVSS score of 5.3 (MEDIUM). 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...
How severe is CVE-2022-41316?
CVE-2022-41316 has been rated MEDIUM with a CVSS base score of 5.3/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2022-41316?
Check the references section above for vendor advisories and patch information. Affected products include: Hashicorp Vault.