Private merge request ID disclosure via activity timeline
Published Feb 14, 2020 · Updated Aug 5, 2024
Information disclosure in GitLab 12.2.2 and earlier allows remote authenticated users to view a private merge request ID. The issue activity timeline renders a cross-referenced merge request identifier without checking whether the guest can view the associated merge request. Guest membership in the private project and access to the linked issue are required; exposure is limited to the merge request identifier.
Summary
What happened
Information disclosure in GitLab 12.2.2 and earlier allows remote authenticated users to view a private merge request ID. The issue activity timeline renders a cross-referenced merge request identifier without checking whether the guest can view the associated merge request. Guest membership in the private project and access to the linked issue are required; exposure is limited to the merge request identifier.
The record
- CVE
- CVE-2019-15592
- Published
- Feb 14, 2020
- Updated
- Aug 5, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-200, T1213.003
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 14, 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=12.2.3
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
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