Milestone disclosure via release API authorization bypass
Published Jan 13, 2020 · Updated Aug 5, 2024
Access control failure in GitLab CE and EE 12.6 allows remote attackers to read restricted milestone data through the releases API. The releases API serializes milestones associated with a public-project release without enforcing the milestone read permission. A public project with issue and merge-request visibility limited to members exposes milestone titles, descriptions, dates, and URLs without authentication.
Summary
What happened
Access control failure in GitLab CE and EE 12.6 allows remote attackers to read restricted milestone data through the releases API. The releases API serializes milestones associated with a public-project release without enforcing the milestone read permission. A public project with issue and merge-request visibility limited to members exposes milestone titles, descriptions, dates, and URLs without authentication.
The record
- CVE
- CVE-2019-20143
- Published
- Jan 13, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-306
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 13, 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?
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
- Unauthenticated release-milestone disclosure reproducerproof 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