CVE-2022-41316GHSA-9MH8-9J64-443FBIT-VAULT-2022-41316GO-2023-1897
HashiCorp Vault and Vault Enterprise’s TLS certificate auth method did not initially load the optionally configured CRL issued by the role's
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.11.4, 1.10.7, 1.9.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- n/a n/a
Version range not reported
- github.com/hashicorp/vaultGo
From 1.11.0 · fixed in 1.11.4
- github.com/hashicorp/vaultGo
From 1.10.0 · fixed in 1.10.7
- github.com/hashicorp/vaultGo
fixed in 1.9.10
- github.com/hashicorp/vaultGo
fixed in 1.9.10; From 1.10.0 · fixed in 1.10.7; From 1.11.0 · fixed in 1.11.4