Authenticated permission bypass via internal project creation
Published Mar 10, 2020 · Updated Aug 4, 2024
Improper input validation in GitLab CE and EE 11.7 through 11.11 allows remote authenticated users to bypass private-group permissions. The project-creation path accepts Internal visibility for a project inside a Private group without enforcing the parent group's stricter visibility. A user able to create a group project can expose its repository to signed-in nonmembers rather than only private-group members.
Summary
What happened
Improper input validation in GitLab CE and EE 11.7 through 11.11 allows remote authenticated users to bypass private-group permissions. The project-creation path accepts Internal visibility for a project inside a Private group without enforcing the parent group's stricter visibility. A user able to create a group project can expose its repository to signed-in nonmembers rather than only private-group members.
The record
- CVE
- CVE-2019-12433
- Published
- Mar 10, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 10, 2020CVE 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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