CVE-2019-9218
First published: Wed May 29 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 1 of 5).
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | <11.6.10 | |
| GitLab | <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-9218?
The severity of CVE-2019-9218 is considered medium due to its incorrect access control issue.
How do I fix CVE-2019-9218?
To fix CVE-2019-9218, upgrade GitLab Community or Enterprise Edition to version 11.6.10 or later, or to version 11.7.6 or later.
What versions are affected by CVE-2019-9218?
CVE-2019-9218 affects GitLab Community and Enterprise Editions before 11.6.10, 11.7.x before 11.7.6, and 11.8.x before 11.8.1.
What types of products are impacted by CVE-2019-9218?
CVE-2019-9218 impacts both GitLab Community and Enterprise Editions.
Is there a workaround for CVE-2019-9218?
There is no documented workaround for CVE-2019-9218; updating to the patched versions is required.
- agent/type
- agent/references
- 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/11.7.0
- version/gitlab/11.8.0