Persistent project access via unrevoked tokens
Published Oct 5, 2021 · Updated Aug 4, 2024
Improper access control in affected GitLab releases allows remote authenticated users to retain project access after deletion. The project deletion path fails to remove related project access tokens, leaving their bot credentials valid after the project is deleted. A user who can create a project access token and delete its project can continue reading and modifying resources allowed by that token.
Summary
What happened
Improper access control in affected GitLab releases allows remote authenticated users to retain project access after deletion. The project deletion path fails to remove related project access tokens, leaving their bot credentials valid after the project is deleted. A user who can create a project access token and delete its project can continue reading and modifying resources allowed by that token.
The record
- CVE
- CVE-2021-39866
- Published
- Oct 5, 2021
- Updated
- Aug 4, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- T1078
- Attack vector
- network
- Privileges
- authenticated
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=>=13.6, <14.1.7
- Affected versionversion=>=14.2, <14.2.5
- Affected versionversion=>=14.3, <14.3.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