CVE-2019-16170
First published: Mon 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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=11.6.0<12.0.9 | |
| GitLab | >=11.6.0<12.0.9 | |
| GitLab | >=12.1.0<12.1.9 | |
| GitLab | >=12.1.0<12.1.9 | |
| GitLab | >=12.2.0<12.2.5 | |
| GitLab | >=12.2.0<12.2.5 |
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-16170?
CVE-2019-16170 is considered a critical vulnerability due to incorrect access control in GitLab.
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.
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.
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.
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.
- agent/type
- agent/references
- agent/author
- agent/severity
- agent/softwarecombine
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/first-publish-date
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/gitlab
- canonical/gitlab
- version/gitlab/11.6.0
- version/gitlab/12.1.0
- version/gitlab/12.2.0