Pipeline information disclosure via unchecked API field
Published Mar 10, 2020 · Updated Aug 4, 2024
Incorrect access control in GitLab CE and EE 11.10 through 12.0.2 allows remote authenticated users to read restricted pipeline data. The MergeRequest API entity exposes head_pipeline unconditionally without checking read_pipeline authorization for callers who can view the merge request. A non-project member with an account and merge-request access can enumerate pipeline details even when public pipelines are disabled.
Summary
What happened
Incorrect access control in GitLab CE and EE 11.10 through 12.0.2 allows remote authenticated users to read restricted pipeline data. The MergeRequest API entity exposes head_pipeline unconditionally without checking read_pipeline authorization for callers who can view the merge request. A non-project member with an account and merge-request access can enumerate pipeline details even when public pipelines are disabled.
The record
- CVE
- CVE-2019-13002
- Published
- Mar 10, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1213.003
- 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
- Merge-request API head_pipeline disclosure reproductionfunctional · 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