CVE-2018-16049: Critical severity gitlab vulnerability
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 Sensitive Data Disclosure in Sidekiq Logs through an Error Message.
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 is the severity of CVE-2018-16049?
CVE-2018-16049 has a medium severity rating due to its potential for sensitive data disclosure.
2
How do I fix CVE-2018-16049?
To fix CVE-2018-16049, upgrade GitLab Community or Enterprise Edition to version 11.0.6, 11.1.5, or 11.2.2 or later.
3
Which versions of GitLab are affected by CVE-2018-16049?
CVE-2018-16049 affects GitLab versions before 11.0.6, 11.1.x before 11.1.5, and 11.2.x before 11.2.2.
4
What kind of data can be exposed due to CVE-2018-16049?
CVE-2018-16049 may lead to the exposure of sensitive data through Sidekiq logs.
5
Is CVE-2018-16049 related to GitLab Community and Enterprise Editions?
Yes, CVE-2018-16049 affects both GitLab Community and Enterprise Editions.