Post-deletion API access via retained group token
Published Aug 5, 2022 · Updated Aug 3, 2024
Incomplete cleanup in GitLab CE/EE affected releases allows remote authenticated users to retain a group access token after its group is deleted. Group deletion fails to cascade into the associated bot user and personal access token, leaving the credential valid for limited API operations. Exploitation requires Group Owner access, an existing group access token, and deletion of its group; access remains bounded by the token's original scopes.
Summary
What happened
Incomplete cleanup in GitLab CE/EE affected releases allows remote authenticated users to retain a group access token after its group is deleted. Group deletion fails to cascade into the associated bot user and personal access token, leaving the credential valid for limited API operations. Exploitation requires Group Owner access, an existing group access token, and deletion of its group; access remains bounded by the token's original scopes.
The record
- CVE
- CVE-2022-2307
- Published
- Aug 5, 2022
- Updated
- Aug 3, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 5, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=>=13.0, <15.0.5
- Affected versionversion=>=15.1, <15.1.4
- Affected versionversion=>=15.2, <15.2.1
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