In all versions of GitLab CE/EE since version 8.0, access tokens created as part of admins impersonation of a user are not cleared at the end of impersonation which may lead to unnecessary sensitive info disclosure.
The product stores, transfers, or shares a resource that contains sensitive information, but it does not properly remove that information before the product makes the resource available to unauthorized actors.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Gitlab | Gitlab | 8.0.0 (including) | 14.1.7 (excluding) |
| Gitlab | Gitlab | 14.2.0 (including) | 14.2.5 (excluding) |
| Gitlab | Gitlab | 14.3.0 (including) | 14.3.1 (excluding) |
| Gitlab | Ubuntu | esm-apps/xenial | * |
| Gitlab | Ubuntu | xenial | * |
Resources that may contain sensitive data include documents, packets, messages, databases, etc. While this data may be useful to an individual user or small set of users who share the resource, it may need to be removed before the resource can be shared outside of the trusted group. The process of removal is sometimes called cleansing or scrubbing. For example, a product for editing documents might not remove sensitive data such as reviewer comments or the local pathname where the document is stored. Or, a proxy might not remove an internal IP address from headers before making an outgoing request to an Internet site.