GitHub Advisoryadvisory · Go
GHSA-jg74-mwgw-v6x3 Vault SSH Secrets Engine Configuration Did Not Restrict Valid Principals By Default
HIGH
Official page ↗
- Aliases
- CVE-2024-7594
- Ecosystem
- Go
- Packages
- github.com/hashicorp/vault, github.com/openbao/openbao
- Severity
- High
- CVSS vector
- CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weaknesses
- CWE-732
- Reviewed
- 2024-09-26
Affected packages
• Go github.com/hashicorp/vault: >= 1.7.7, < 1.17.6 → fixed in 1.17.6
• Go github.com/openbao/openbao: < 2.0.2 (no fix yet)
• Go github.com/openbao/openbao: < 0.0.0-20241003222810-d5b4e9224698 → fixed in 0.0.0-20241003222810-d5b4e9224698
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.
Related
Alias · CVE (1)
- CVE-2024-7594 Vault’s SSH secrets engine did not require the valid_principals list to contain a value by default. vulnerability
Weakness · CWE (1)
- CWE-732 Incorrect Permission Assignment for Critical Resource weakness
References
- https://nvd.nist.gov/vuln/detail/CVE-2024-7594 advisory
- https://github.com/openbao/openbao/pull/561 web
- https://github.com/openbao/openbao/commit/d5b4e922469830ac335b21dc0e8f9878c501a884 web
- https://discuss.hashicorp.com/t/hcsec-2024-20-vault-ssh-secrets-engine-configuration-did-not-restrict-valid-principals-by-default/70251 web
- https://github.com/hashicorp/vault package
- https://openbao.org/docs/release-notes/2-0-0/#202 web
- https://pkg.go.dev/vuln/GO-2024-3162 web
- https://security.netapp.com/advisory/ntap-20250110-0007 web