CVE-2019-9170: 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.
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:23 PM
Data Sourced
via MITRE·04:23 PM
Description
Data Sourced
via NVD·05:29 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2019-9170?
CVE-2019-9170 has been classified with a high severity due to the potential for unauthorized access to sensitive information.
2
How do I fix CVE-2019-9170?
To fix CVE-2019-9170, upgrade GitLab to versions 11.6.10, 11.7.6, or 11.8.1 or later.
3
What causes the issue in CVE-2019-9170?
CVE-2019-9170 is caused by incorrect access control settings that allow users to access restricted resources.
4
Which versions of GitLab are affected by CVE-2019-9170?
CVE-2019-9170 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.
5
Is there a workaround for CVE-2019-9170?
There is no recommended workaround for CVE-2019-9170; upgrading to the secure versions is the best course of action.