CVE-2018-16051: Infoleak
Published Oct 3, 2018
·Updated
An issue was discovered in GitLab Community and Enterprise Edition before 11.0.6, 11.1.x before 11.1.5, and 11.2.x before 11.2.2. There is Orphaned Upload Files Exposure.
Affected Software
6 affected components
GitLab GitLab>=8.10.0<11.0.6
GitLab GitLab>=8.10.0<11.0.6
GitLab GitLab>=11.1.0<11.1.5
GitLab GitLab>=11.1.0<11.1.5
GitLab GitLab>=11.2.0<11.2.2
GitLab GitLab>=11.2.0<11.2.2
Event History
Oct 3, 2018
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
Description
Frequently Asked Questions
1
What versions of GitLab are affected by CVE-2018-16051?
CVE-2018-16051 affects GitLab Community and Enterprise Editions before version 11.0.6, 11.1.x before 11.1.5, and 11.2.x before 11.2.2.
2
What is the nature of the vulnerability identified in CVE-2018-16051?
CVE-2018-16051 involves exposure of orphaned upload files in GitLab.
3
How can I mitigate CVE-2018-16051 in my GitLab installation?
To mitigate CVE-2018-16051, upgrade GitLab to version 11.0.6, 11.1.5, or 11.2.2 or later.
4
Is there a known exploit for CVE-2018-16051?
There are no known exploits publicly available for CVE-2018-16051 at this time.
5
What should I do if I am unable to upgrade to a fixed version for CVE-2018-16051?
If unable to upgrade, consider implementing controls to limit access to sensitive upload files as a temporary measure against CVE-2018-16051.