CVE-2019-9219: 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 has Incorrect Access Control (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:43 PM
Data Sourced
via MITRE·04:43 PM
Description
Data Sourced
via NVD·05:29 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2019-9219?
CVE-2019-9219 has been classified with a severity rating that reflects its potential impact on systems using affected versions of GitLab.
2
How do I fix CVE-2019-9219?
The recommended fix for CVE-2019-9219 is to upgrade to GitLab versions 11.6.10, 11.7.6, or 11.8.1 or later.
3
What versions of GitLab are affected by CVE-2019-9219?
CVE-2019-9219 affects GitLab Community and Enterprise Editions prior to 11.6.10, 11.7.x before 11.7.6, and 11.8.x before 11.8.1.
4
What type of vulnerability is CVE-2019-9219?
CVE-2019-9219 is categorized as an Incorrect Access Control vulnerability.
5
What is the impact of CVE-2019-9219 on GitLab users?
The impact of CVE-2019-9219 may include unauthorized access to sensitive data or resources within GitLab installations.