All reports
High

Vault SSH Secrets Engine Configuration Did Not Restrict Valid Principals By Default

Affected versions

Version ranges need review.

Affected versions
>=1.7.7 <1.17.6
Fixed version
1.17.6
Affected versions
>= 1.7.7, < 1.17.6
Fixed version
1.17.6
Affected versions
>= 0.1.0, < 2.0.2
Fixed version
Not reported
Affected versions
< 0.0.0-20241003222810-d5b4e9224698
Fixed version
0.0.0-20241003222810-d5b4e9224698
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2024-7594

Probability of exploitation in the next 30 days: 0.27%

FIRST EPSS · 2026-11-19

Description

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.

Links

Credits

  • westonsteimel
  • cipherboy