CVE-2019-9223: High 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.
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:50 PM
Data Sourced
via MITRE·04:50 PM
Description
Data Sourced
via NVD·05:29 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2019-9223?
CVE-2019-9223 is classified as a medium severity vulnerability due to information exposure risks.
2
How do I fix CVE-2019-9223?
To fix CVE-2019-9223, upgrade GitLab to the latest version beyond 11.6.10, 11.7.6, or 11.8.1 as applicable.
3
What versions are affected by CVE-2019-9223?
CVE-2019-9223 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-9223?
CVE-2019-9223 is categorized as an Information Exposure vulnerability.
5
Can I still use my affected GitLab version safely?
Using an affected GitLab version poses security risks, and it is recommended to update to a non-vulnerable version.