Vault SSH Secrets Engine Configuration Did Not Restrict Valid Principals By Default
HashiCorp Vault · HashiCorp Vault Enterprise
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/hashicorp/vault Go |
|
|
| github.com/openbao/openbao Go |
|
|
HashiCorp Vault · HashiCorp Vault Enterprise
| Product | Affected | Fixed in |
|---|---|---|
| github.com/hashicorp/vault Go |
|
|
| github.com/openbao/openbao Go |
|
|
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.
From the CVE record · HashiCorp
Vault’s SSH secrets engine did not require a value in valid_principals by default. If neither valid_principals nor default_user is set, a user authorized to request an SSH certificate can use it to authenticate as any user on the host.
Operators of HashiCorp Vault or Vault Enterprise, and users of Go packages github.com/hashicorp/vault >=1.7.7 <1.17.6 or github.com/openbao/openbao >=0.1.0 and <0.0.0-20241003222810-d5b4e9224698, should check their deployments.