Vault Community, Vault Enterprise (“Vault”) Azure Auth method did not correctly validate the claims in the Azure-issued token, resulting in the potential bypass of the bound_locations parameter on login. Fixed in Vault Community Edition 1.19.1 and Vault Enterprise 1.19.1, 1.18.7, 1.17.14, 1.16.18.
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Vault | Hashicorp | 0.10.0 (including) | 1.16.18 (excluding) |
Vault | Hashicorp | 0.10.0 (including) | 1.19.1 (excluding) |
Vault | Hashicorp | 1.17.0 (including) | 1.17.14 (excluding) |
Vault | Hashicorp | 1.18.0 (including) | 1.18.7 (excluding) |
Vault | Hashicorp | 1.19.0 (including) | 1.19.0 (including) |
Assuming a user with a given identity, authorization is the process of determining whether that user can access a given resource, based on the user’s privileges and any permissions or other access-control specifications that apply to the resource. When access control checks are incorrectly applied, users are able to access data or perform actions that they should not be allowed to perform. This can lead to a wide range of problems, including information exposures, denial of service, and arbitrary code execution.