CVE-2019-9732
First published: Wed 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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=10.8.0<=10.8.7 | |
| GitLab | >=10.8.0<=10.8.7 | |
| GitLab | >=11.0.0<11.6.10 | |
| GitLab | >=11.0.0<11.6.10 | |
| GitLab | >=11.7.0<11.7.6 | |
| GitLab | >=11.7.0<11.7.6 | |
| GitLab | >=11.8.0<11.8.1 | |
| GitLab | >=11.8.0<11.8.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2019-9732?
CVE-2019-9732 has a medium severity rating due to its incorrect access control settings.
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.
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.
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.
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.
- agent/references
- agent/type
- agent/author
- agent/severity
- agent/softwarecombine
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/gitlab
- canonical/gitlab
- version/gitlab/10.8.0
- version/gitlab/10.8.7
- version/gitlab/11.0.0
- version/gitlab/11.7.0
- version/gitlab/11.8.0