Incorrect Authorization check affecting all versions of GitLab EE from 13.11 prior to 15.5.7, 15.6 prior to 15.6.4, and 15.7 prior to 15.7.2 allows group access tokens to continue working even after the group owner loses the ability to revoke them.
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 |
---|---|---|---|
Gitlab | Gitlab | 13.11.0 (including) | 15.5.7 (excluding) |
Gitlab | Gitlab | 15.6.0 (including) | 15.6.4 (excluding) |
Gitlab | Gitlab | 15.7.0 (including) | 15.7.2 (excluding) |
Check | Ubuntu | bionic | * |
Check | Ubuntu | kinetic | * |
Check | Ubuntu | lunar | * |
Check | Ubuntu | mantic | * |
Check | Ubuntu | trusty | * |
Check | Ubuntu | xenial | * |
Gitlab | Ubuntu | esm-apps/xenial | * |
Gitlab | Ubuntu | trusty | * |
Gitlab | Ubuntu | xenial | * |
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.