CVE-2019-9171: 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 1 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:37 PM
Data Sourced
via MITRE·04:37 PM
Description
Data Sourced
via NVD·05:29 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2019-9171?
CVE-2019-9171 has been classified as a high severity vulnerability due to information exposure.
2
How do I fix CVE-2019-9171?
To fix CVE-2019-9171, upgrade GitLab to versions 11.6.10, 11.7.6, or 11.8.1 or later.
3
What versions of GitLab are affected by CVE-2019-9171?
CVE-2019-9171 affects GitLab Community and Enterprise Editions up to version 11.6.10, between 11.7.0 and 11.7.6, and between 11.8.0 and 11.8.1.
4
Is CVE-2019-9171 specific to any GitLab editions?
Yes, CVE-2019-9171 affects both GitLab Community Edition and GitLab Enterprise Edition.
5
What type of vulnerability is CVE-2019-9171?
CVE-2019-9171 is classified as an Information Exposure vulnerability.