First published: Mon Sep 09 2019(Updated: )
An issue was discovered in GitLab Community and Enterprise Edition 9.x, 10.x, and 11.x before 11.5.8, 11.6.x before 11.6.6, and 11.7.x before 11.7.1. It has Incorrect Access Control. Access to the internal wiki is permitted when an external wiki service is enabled.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=9.3.0<=9.3.7 | |
GitLab | >=9.3.0<=9.3.7 | |
GitLab | >=10.0.0<=10.8.7 | |
GitLab | >=10.0.0<=10.8.7 | |
GitLab | >=11.0.0<11.5.8 | |
GitLab | >=11.0.0<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 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-6960 has a medium severity rating due to incorrect access control allowing unauthorized access to the internal wiki.
To fix CVE-2019-6960, upgrade GitLab to the patched versions 11.5.8, 11.6.6, or 11.7.1 or later.
CVE-2019-6960 affects GitLab Community and Enterprise Editions 9.x, 10.x, and 11.x before specific patched versions.
Exploiting CVE-2019-6960 could allow an attacker to gain unauthorized access to sensitive internal wiki content.
Yes, disabling the external wiki service can act as a temporary mitigation until the software is updated.