Unauthorized deployment access via unchecked group identifier
Published Jan 28, 2020 · Updated Aug 5, 2024
Authorization bypass in GitLab EE before 12.1.12, 12.2.6, or 12.3.2 allows remote authenticated users to add private groups to protected environments. The protected-environment creation endpoint accepts a client-controlled group_id without checking that the group is shared with the project. Maintainer access is required, and successful exploitation grants the selected private group deployment access without disclosing its name.
Summary
What happened
Authorization bypass in GitLab EE before 12.1.12, 12.2.6, or 12.3.2 allows remote authenticated users to add private groups to protected environments. The protected-environment creation endpoint accepts a client-controlled group_id without checking that the group is shared with the project. Maintainer access is required, and successful exploitation grants the selected private group deployment access without disclosing its name.
The record
- CVE
- CVE-2019-15582
- Published
- Jan 28, 2020
- Updated
- Aug 5, 2024
- Vendor
- GitLab
- Product
- GitLab EE
- Classifications
- CWE-639, T1098
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 28, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=before 12.1.12
- Affected versionversion=before 12.2.6
- Affected versionversion=before 12.3.2
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
- Protected-environment group_id request 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