First published: Thu Mar 22 2018(Updated: )
GitLab Community and Enterprise Editions before 10.1.6, 10.2.6, and 10.3.4 are vulnerable to an authorization bypass issue in the Projects::MergeRequests::CreationsController component resulting in an attacker to see every project name and their respective namespace on a GitLab instance.
Credit: support@hackerone.com
Affected Software | Affected Version | How to fix |
---|---|---|
debian/gitlab | 16.0.8+ds1-2 | |
GitLab | >8.8.0<=10.1.5 | |
GitLab | >=8.8.0<=10.1.5 | |
GitLab | >10.2.0<=10.2.5 | |
GitLab | >=10.2.0<=10.2.5 | |
GitLab | >10.3.0<=10.3.3 | |
GitLab | >=10.3.0<=10.3.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-0920 has a severity rating that indicates a significant risk due to authorization bypass allowing project enumeration.
To fix CVE-2017-0920, upgrade your GitLab installation to versions 10.1.6, 10.2.6, or 10.3.4 and above.
CVE-2017-0920 affects users of GitLab Community and Enterprise Editions prior to versions 10.1.6, 10.2.6, and 10.3.4.
CVE-2017-0920 is classified as an authorization bypass vulnerability.
Yes, CVE-2017-0920 allows attackers to see the names and namespaces of all projects on a GitLab instance without proper authorization.