CVE-2019-6791
First published: Mon Sep 09 2019(Updated: )
An issue was discovered in GitLab Community and Enterprise Edition before 11.5.8, 11.6.x before 11.6.6, and 11.7.x before 11.7.1. It has Incorrect Access Control (issue 3 of 3). When a project with visibility more permissive than the target group is imported, it will retain its prior visibility.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | <11.5.8 | |
| GitLab | <11.5.8 | |
| GitLab | >=11.6.0<11.6.6 | |
| GitLab | >=11.6.0<11.6.6 | |
| GitLab | >=11.7.0<11.7.1 | |
| GitLab | >=11.7.0<11.7.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.
Frequently Asked Questions
What is the severity of CVE-2019-6791?
CVE-2019-6791 has a medium severity due to its incorrect access control vulnerability.
How do I fix CVE-2019-6791?
To fix CVE-2019-6791, upgrade your GitLab instance to version 11.5.8, 11.6.6, or 11.7.1 or later.
What versions are affected by CVE-2019-6791?
CVE-2019-6791 affects GitLab Community and Enterprise Editions prior to 11.5.8, 11.6.6, and 11.7.1.
What is the impact of CVE-2019-6791?
The impact of CVE-2019-6791 allows an imported project to retain a more permissive visibility than intended.
Is CVE-2019-6791 a serious issue for GitLab users?
Yes, CVE-2019-6791 is a serious issue as it can lead to unauthorized access to private project information.
- agent/type
- agent/references
- agent/weakness
- 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/11.7.0