CVE-2024-7594GO-2024-3162BIT-OPENBAO-2024-7594BIT-VAULT-2024-7594GHSA-JG74-MWGW-V6X3
Vault SSH Secrets Engine Configuration Did Not Restrict Valid Principals By Default
- 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.17.6, 1.15.15, 0.0.0-20241003222810-d5b4e9224698
- 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: no
- Technical impact: total
Summary
Vault’s SSH secrets engine did not require the valid_principals list to contain a value by default. If the valid_principals and default_user fields of the SSH secrets engine configuration are not set, an SSH certificate requested by an authorized user to Vault’s SSH secrets engine could be used to authenticate as any user on the host. Fixed in Vault Community Edition 1.17.6, and in Vault Enterprise 1.17.6, 1.16.10, and 1.15.15.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- HashiCorp Vault
From 1.7.7 · fixed in 1.17.6
- HashiCorp Vault Enterprise
From 1.7.7 · fixed in 1.15.15
- github.com/hashicorp/vaultGo
From 1.7.7 · fixed in 1.17.6
- github.com/openbao/openbaoGo
From 0.1.0
- github.com/openbao/openbaoGo
fixed in 0.0.0-20241003222810-d5b4e9224698