Unauthorized project access via stale inherited permissions
Published Nov 4, 2021 · Updated Aug 4, 2024
Improper access control in GitLab 12.9 through 13.0.0 allows remote authenticated users to retain unauthorized access to private projects. Group-transfer handling grants access from the new parent hierarchy but fails to revoke inherited project permissions from members of the old parent. A project must be shared with a subgroup and that subgroup transferred; affected members can keep hidden access up to the invited role, including Maintainer.
Summary
What happened
Improper access control in GitLab 12.9 through 13.0.0 allows remote authenticated users to retain unauthorized access to private projects. Group-transfer handling grants access from the new parent hierarchy but fails to revoke inherited project permissions from members of the old parent. A project must be shared with a subgroup and that subgroup transferred; affected members can keep hidden access up to the invited role, including Maintainer.
The record
- CVE
- CVE-2021-39897
- Published
- Nov 4, 2021
- Updated
- Aug 4, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-281, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 4, 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=>=12.10, <12.10.7
- Affected versionversion=>=12.9, <12.9.8
- Affected versionversion=>=13.0, <13.0.1
What conditions does exploitation require?
What is affected?
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
- GitLab subgroup-transfer access-retention reproductionproof 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