CVE-2019-16170: High severity gitlab vulnerability
Published Sep 16, 2019
·Updated
An issue was discovered in GitLab Enterprise Edition 11.x and 12.x before 12.0.9, 12.1.x before 12.1.9, and 12.2.x before 12.2.5. It has Incorrect Access Control.
Affected Software
6 affected components
GitLab GitLab>=11.6.0<12.0.9
GitLab GitLab>=11.6.0<12.0.9
GitLab GitLab>=12.1.0<12.1.9
GitLab GitLab>=12.1.0<12.1.9
GitLab GitLab>=12.2.0<12.2.5
GitLab GitLab>=12.2.0<12.2.5
Event History
Sep 16, 2019
CVE Published
via MITRE·11:59 AM
Data Sourced
via MITRE·11:59 AM
Description
Frequently Asked Questions
1
What is the severity of CVE-2019-16170?
CVE-2019-16170 is considered a critical vulnerability due to incorrect access control in GitLab.
2
How do I fix CVE-2019-16170?
To fix CVE-2019-16170, upgrade GitLab to version 12.0.9, 12.1.9, or 12.2.5 or later.
3
What versions of GitLab are affected by CVE-2019-16170?
CVE-2019-16170 affects GitLab Enterprise Edition and Community Edition versions 11.x and 12.x prior to 12.0.9, 12.1.9, and 12.2.5.
4
What is the nature of the vulnerability described in CVE-2019-16170?
CVE-2019-16170 involves an issue of incorrect access control that could allow unauthorized access.
5
Is CVE-2019-16170 present in all GitLab versions?
No, CVE-2019-16170 is only present in specific earlier versions of GitLab before the mentioned patches.