CVE-2019-9179: 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 5 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:31 PM
Data Sourced
via MITRE·04:31 PM
Description
Data Sourced
via NVD·05:29 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2019-9179?
The severity of CVE-2019-9179 is classified as medium, indicating a moderate risk of information exposure.
2
How do I fix CVE-2019-9179?
To fix CVE-2019-9179, users should upgrade to GitLab Community or Enterprise Edition version 11.6.10, 11.7.6, or 11.8.1 or later.
3
What does CVE-2019-9179 affect?
CVE-2019-9179 affects various versions of GitLab Community and Enterprise Editions prior to specific patched versions.
4
What type of vulnerability is CVE-2019-9179?
CVE-2019-9179 is categorized as an Information Exposure vulnerability.
5
When was CVE-2019-9179 disclosed?
CVE-2019-9179 was disclosed in March 2019, affecting multiple earlier versions of GitLab.