CVE-2019-9732: Critical severity gitlab vulnerability
Published May 29, 2019
·Updated
An issue was discovered in GitLab Community and Enterprise Edition 10.x (starting from 10.8) and 11.x 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
8 affected components
GitLab GitLab>=10.8.0<=10.8.7
GitLab GitLab>=10.8.0<=10.8.7
GitLab GitLab>=11.0.0<11.6.10
GitLab GitLab>=11.0.0<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
May 29, 2019
CVE Published
via MITRE·04:18 PM
Data Sourced
via MITRE·04:18 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2019-9732?
CVE-2019-9732 has a medium severity rating due to its incorrect access control settings.
2
How do I fix CVE-2019-9732?
To fix CVE-2019-9732, upgrade GitLab Community or Enterprise Edition to the latest version that resolves this vulnerability.
3
Which versions of GitLab are affected by CVE-2019-9732?
CVE-2019-9732 affects GitLab Community and Enterprise Editions from version 10.8 to less than 11.8.1.
4
What types of impact can CVE-2019-9732 have on my GitLab installation?
CVE-2019-9732 can potentially allow unauthorized access to certain functionalities within GitLab, compromising data security.
5
Is CVE-2019-9732 present in all GitLab versions?
No, CVE-2019-9732 is present only in specific versions of GitLab from 10.8 to versions before 11.8.1.