Vulnerability feedback disclosure via missing endpoint authorization
Published Jan 28, 2020 · Updated Aug 4, 2024
Information disclosure in GitLab before 11.11.6, 12.0.4, and 12.1.2 allows remote attackers to read vulnerability feedback. The vulnerability_feedback endpoint applies the general read_project permission instead of the finer-grained dashboard and pipeline access rules. Public projects permit unauthenticated access, while internal or private project exposure depends on low-privilege visibility; responses reveal dismissed vulnerability types and shared project fingerprints.
Summary
What happened
Information disclosure in GitLab before 11.11.6, 12.0.4, and 12.1.2 allows remote attackers to read vulnerability feedback. The vulnerability_feedback endpoint applies the general read_project permission instead of the finer-grained dashboard and pipeline access rules. Public projects permit unauthenticated access, while internal or private project exposure depends on low-privilege visibility; responses reveal dismissed vulnerability types and shared project fingerprints.
The record
- CVE
- CVE-2019-5470
- Published
- Jan 28, 2020
- Updated
- Aug 4, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-862, CWE-200, T1190
- Attack vector
- network
- Privileges
- unauthenticated
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=before 11.11.6
- Affected versionversion=before 12.0.4
- Affected versionversion=before 12.1.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
- Direct vulnerability_feedback endpoint requestproof 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