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.

What is the nature of the vulnerability identified in CVE-2018-16051?

CVE-2018-16051 involves exposure of orphaned upload files in GitLab.

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.

Is there a known exploit for CVE-2018-16051?

There are no known exploits publicly available for CVE-2018-16051 at this time.

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.

Vulnerability/
CVE-2018-16051

medium

6.5

CWE

200

3/10/2018

5/8/2024

CVE-2018-16051: Infoleak

First published: Wed Oct 03 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.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=8.10.0<11.0.6
GitLab	>=8.10.0<11.0.6
GitLab	>=11.1.0<11.1.5
GitLab	>=11.1.0<11.1.5
GitLab	>=11.2.0<11.2.2
GitLab	>=11.2.0<11.2.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

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.
What is the nature of the vulnerability identified in CVE-2018-16051?
CVE-2018-16051 involves exposure of orphaned upload files in GitLab.
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.
Is there a known exploit for CVE-2018-16051?
There are no known exploits publicly available for CVE-2018-16051 at this time.
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.

agent/references
agent/type
agent/severity
agent/weakness
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/8.10.0
version/gitlab/11.1.0
version/gitlab/11.2.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

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.
What is the nature of the vulnerability identified in CVE-2018-16051?
CVE-2018-16051 involves exposure of orphaned upload files in GitLab.
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.
Is there a known exploit for CVE-2018-16051?
There are no known exploits publicly available for CVE-2018-16051 at this time.
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.