CVE-2019-9175: Infoleak
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 3 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:26 PM
Data Sourced
via MITRE·04:26 PM
Description
Data Sourced
via NVD·05:29 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2019-9175?
CVE-2019-9175 is classified as an Information Exposure vulnerability.
2
How do I fix CVE-2019-9175?
To mitigate CVE-2019-9175, upgrade to GitLab Community Edition and Enterprise Edition version 11.6.10 or later.
3
Which versions are affected by CVE-2019-9175?
CVE-2019-9175 affects GitLab versions before 11.6.10, 11.7.x before 11.7.6, and 11.8.x before 11.8.1.
4
What kind of issues does CVE-2019-9175 cause?
CVE-2019-9175 allows unauthorized information exposure within the affected versions of GitLab.
5
What are the GitLab versions that resolve CVE-2019-9175?
The vulnerability CVE-2019-9175 is resolved in GitLab versions 11.6.10, 11.7.6, and 11.8.1 or later.