Vault SSH Secrets Engine Configuration Did Not Restrict Valid Principals By Default
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Vault 1.17.6.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| HashiCorp | Vault | >=1.7.7 <1.17.6 | 1.17.6 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in HashiCorp, strongest first
Embed
A live severity badge for an advisory, README or ticket