CVE-2019-6787: Medium severity gitlab vulnerability
Published May 17, 2019
·Updated
An Incorrect Access Control 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. The GitLab API allowed project Maintainers and Owners to view the trigger tokens of other project users.
Affected Software
6 affected components
GitLab GitLab>=8.12.0<11.5.8
GitLab GitLab>=8.12.0<11.5.8
GitLab GitLab>=11.6.0<11.6.6
GitLab GitLab>=11.6.0<11.6.6
GitLab GitLab>=11.7.0<11.7.1
GitLab GitLab>=11.7.0<11.7.1
Event History
May 17, 2019
CVE Published
via MITRE·03:49 PM
Data Sourced
via MITRE·03:49 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2019-6787?
CVE-2019-6787 has a medium severity level due to the potential exposure of sensitive trigger tokens.
2
How do I fix CVE-2019-6787?
To fix CVE-2019-6787, upgrade GitLab to version 11.5.8, 11.6.6, or 11.7.1 or newer.
3
What systems are affected by CVE-2019-6787?
CVE-2019-6787 affects GitLab Community and Enterprise Editions prior to versions 11.5.8, 11.6.6, and 11.7.1.
4
Who is impacted by CVE-2019-6787?
Project Maintainers and Owners in GitLab can be impacted by CVE-2019-6787 as they can view the trigger tokens of other users.
5
What type of vulnerability is CVE-2019-6787?
CVE-2019-6787 is categorized as an Incorrect Access Control vulnerability.