Sensitive data disclosure via uncleared impersonation tokens
Published Oct 5, 2021 · Updated Aug 4, 2024
Improper access control in GitLab allows remote authenticated users to retain access tokens after administrator impersonation ends. The impersonation session lifecycle leaves session access tokens uncleared when impersonation starts or stops, allowing token-backed access to outlive the session. Administrator access and enabled impersonation are required; retained tokens expose user-scoped information and authorize actions within their scopes.
Summary
What happened
Improper access control in GitLab allows remote authenticated users to retain access tokens after administrator impersonation ends. The impersonation session lifecycle leaves session access tokens uncleared when impersonation starts or stops, allowing token-backed access to outlive the session. Administrator access and enabled impersonation are required; retained tokens expose user-scoped information and authorize actions within their scopes.
The record
- CVE
- CVE-2021-39891
- Published
- Oct 5, 2021
- Updated
- Aug 4, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-212, T1550.001
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Oct 5, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>=14.2, <14.2.5
- Affected versionversion=>=14.3, <14.3.1
- Affected versionversion=>=8.0, <14.1.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo