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.

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.

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.

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.

What type of vulnerability is CVE-2019-6787?

CVE-2019-6787 is categorized as an Incorrect Access Control vulnerability.

Vulnerability/
CVE-2019-6787

medium

6.5

17/5/2019

4/8/2024

CVE-2019-6787

First published: Fri 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.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=8.12.0<11.5.8
GitLab	>=8.12.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

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

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.
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.
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.
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.
What type of vulnerability is CVE-2019-6787?
CVE-2019-6787 is categorized as an Incorrect Access Control vulnerability.

agent/references
agent/type
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/8.12.0
version/gitlab/11.6.0
version/gitlab/11.7.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

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.
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.
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.
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.
What type of vulnerability is CVE-2019-6787?
CVE-2019-6787 is categorized as an Incorrect Access Control vulnerability.