Vault SSH Secrets Engine Configuration Did Not Restrict Valid Principals By Default
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| HashiCorp | Vault | unaffected |
|
||||||
| HashiCorp | Vault Enterprise | unaffected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-2820 | 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. |
Github GHSA |
GHSA-jg74-mwgw-v6x3 | Vault SSH Secrets Engine Configuration Did Not Restrict Valid Principals By Default |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.269% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Openbao
Openbao openbao |
|
| CPEs | cpe:2.3:a:openbao:openbao:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Openbao
Openbao openbao |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Hashicorp vault
|
|
| CPEs | cpe:2.3:a:hashicorp:vault:*:*:*:*:-:*:*:* cpe:2.3:a:hashicorp:vault:*:*:*:*:enterprise:*:*:* |
|
| Vendors & Products |
Hashicorp vault
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
epss
|
epss
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Hashicorp
Hashicorp vault Community Edition Hashicorp vault Enterprise |
|
| CPEs | cpe:2.3:a:hashicorp:vault_community_edition:*:*:*:*:*:*:*:* cpe:2.3:a:hashicorp:vault_enterprise:*:*:*:*:*:*:*:* |
|
| Vendors & Products |
Hashicorp
Hashicorp vault Community Edition Hashicorp vault Enterprise |
|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | 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. |
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Vault SSH Secrets Engine Configuration Did Not Restrict Valid Principals By Default | |
| Weaknesses | CWE-732 | |
| References |
| |
| Metrics |
cvssV3_1
|