Private label disclosure via unchecked label IDs
Published Jan 28, 2020 · Updated Aug 4, 2024
IDOR in GitLab CE/EE 11.5 and later allows remote authenticated users to read private-project label names through merge-request creation. The new merge-request endpoint accepts user-controlled sequential label_ids values and renders the referenced labels without checking project visibility. Membership in any project with permission to create merge requests is sufficient; exposure is limited to label names from otherwise inaccessible projects.
Summary
What happened
IDOR in GitLab CE/EE 11.5 and later allows remote authenticated users to read private-project label names through merge-request creation. The new merge-request endpoint accepts user-controlled sequential label_ids values and renders the referenced labels without checking project visibility. Membership in any project with permission to create merge requests is sufficient; exposure is limited to label names from otherwise inaccessible projects.
The record
- CVE
- CVE-2019-5466
- Published
- Jan 28, 2020
- Updated
- Aug 4, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-639, T1213.003
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 28, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Affects GitLab CE/EE 11.5 and later
- Affected versionversion=Fixed in 12.1.2 in 12.0.4 and in 11.11.6
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
- Crafted merge-request label-ID 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