CVE-2019-9170
First published: Wed 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.
Credit: cve@mitre.org 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-9170?
CVE-2019-9170 has been classified with a high severity due to the potential for unauthorized access to sensitive information.
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.
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.
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.
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.
- agent/type
- agent/references
- agent/weakness
- agent/severity
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/first-publish-date
- agent/last-modified-date
- agent/author
- agent/softwarecombine
- agent/event
- agent/source
- agent/tags
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/nvd-index
- vendor/gitlab
- canonical/gitlab
- version/gitlab/11.7.0
- version/gitlab/11.8.0