CVE-2024-2048GHSA-R3W7-MFPM-C2VWBIT-VAULT-2024-2048GO-2024-2617
Vault Cert Auth Method Did Not Correctly Validate Non-CA Certificates
- 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.14.10, 1.15.5
- 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: poc
- Automatable: no
- Technical impact: total
Summary
Vault and Vault Enterprise (“Vault”) TLS certificate auth method did not correctly validate client certificates when configured with a non-CA certificate as trusted certificate. In this configuration, an attacker may be able to craft a malicious certificate that could be used to bypass authentication. Fixed in Vault 1.15.5 and 1.14.10.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- HashiCorp Vault
From 1.15.5 · fixed in 1.14.10
- HashiCorp Vault Enterprise
From 1.15.5 · fixed in 1.14.10
- github.com/hashicorp/vaultGo
From 1.15.0 · fixed in 1.15.5
- github.com/hashicorp/vaultGo
fixed in 1.14.10
- github.com/hashicorp/vaultGo
fixed in 1.14.10; From 1.15.0 · fixed in 1.15.5