Vault SSH Secrets Engine Configuration Did Not Restrict Valid Principals By Default
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2024-7594US | high8.8 | — | ||
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 config… | ||||
02
references
External citations — patches, advisories, analysis.
- https://discuss.hashicorp.com/t/hcsec-2024-20-vault-ssh-secrets-engine-configuration-did-not-restrict-valid-principals-by-default/70251WEB
- https://github.com/hashicorp/vaultPACKAGE
- https://github.com/openbao/openbao/commit/d5b4e922469830ac335b21dc0e8f9878c501a884WEB
- https://github.com/openbao/openbao/pull/561WEB
- https://nvd.nist.gov/vuln/detail/CVE-2024-7594ADVISORY
- https://openbao.org/docs/release-notes/2-0-0/#202WEB
- https://pkg.go.dev/vuln/GO-2024-3162WEB
- https://security.netapp.com/advisory/ntap-20250110-0007WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan