Owner escalation via unchecked project-member import
Published Jun 7, 2023 · Updated Jan 7, 2025
Privilege escalation in GitLab 14.1 before 15.10.8, 15.11 before 15.11.7, and 16.0 before 16.0.2 allows attackers to grant Owner access. The project-member import path omits the Owner-role restriction enforced when maintainers invite members or change access levels directly. A project Maintainer must control another project where the imported account is already an Owner; the resulting Owner can delete, archive, or transfer the target project.
Summary
What happened
Privilege escalation in GitLab 14.1 before 15.10.8, 15.11 before 15.11.7, and 16.0 before 16.0.2 allows attackers to grant Owner access. The project-member import path omits the Owner-role restriction enforced when maintainers invite members or change access levels directly. A project Maintainer must control another project where the imported account is already an Owner; the resulting Owner can delete, archive, or transfer the target project.
The record
- CVE
- CVE-2023-2485
- Published
- Jun 7, 2023
- Updated
- Jan 7, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-266, T1098
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 7, 2023CVE publishedPublication date reported by the CVE source.
- Jan 7, 2025Record 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.1, <15.10.8
- Affected versionversion=>=15.11, <15.11.7
- Affected versionversion=>=16.0, <16.0.2
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.
Public exploit references
- Project-member import privilege-escalation proof of conceptproof of concept · demonstrated
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