Vault Operators in Root Namespace May Elevate Their Privileges
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 |
|
|
A privileged Vault operator with write permissions to the root namespace’s identity endpoint could escalate their own or another user’s privileges to Vault’s root policy. Fixed in Vault Community Edition 1.18.0 and Vault Enterprise 1.18.0, 1.17.7, 1.16.11, and 1.15.16.
From the CVE record · HashiCorp
A privileged Vault operator with write access to the root namespace’s identity endpoint can grant themselves or another user Vault’s root policy. This requires those existing permissions; the input does not specify a user-interaction requirement.
Operators running Vault Community Edition or Enterprise, or using Go packages github.com/hashicorp/vault below 1.18.0 or github.com/openbao/openbao below 2.0.3, should check their installations.