CVE-2019-9172: Medium severity gitlab vulnerability
Published Apr 17, 2019
·Updated
An issue was discovered in GitLab Community and Enterprise Edition before 11.6.10, 11.7.x before 11.7.6, and 11.8.x before 11.8.1. It allows Information Exposure (issue 2 of 5).
Affected Software
6 affected components
GitLab GitLab<11.6.10
GitLab GitLab<11.6.10
GitLab GitLab>=11.7.0<11.7.6
GitLab GitLab>=11.7.0<11.7.6
GitLab GitLab>=11.8.0<11.8.1
GitLab GitLab>=11.8.0<11.8.1
Event History
Apr 17, 2019
CVE Published
via MITRE·04:20 PM
Data Sourced
via MITRE·04:20 PM
Description
Data Sourced
via NVD·05:29 PM
DescriptionSeverityAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2019-9172?
CVE-2019-9172 has been classified as an issue that leads to Information Exposure.
2
How do I fix CVE-2019-9172?
To fix CVE-2019-9172, you need to upgrade your GitLab installation to versions 11.6.10, 11.7.6, or 11.8.1 or later.
3
Which versions of GitLab are affected by CVE-2019-9172?
CVE-2019-9172 affects GitLab Community and Enterprise Editions before versions 11.6.10, 11.7.6, and 11.8.1.
4
What type of vulnerability is CVE-2019-9172?
CVE-2019-9172 is a vulnerability that falls under the category of Information Exposure.
5
Can I still use my GitLab version if it is affected by CVE-2019-9172?
It is not recommended to use affected versions of GitLab due to the risk of Information Exposure.