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 allows Information Disclosure (issue 3 of 6). For installations using GitHub or Bitbucket OAuth integrations, it is possible to use a covert redirect to obtain the user OAuth token for those services.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=8.4.0<11.5.8 | |
GitLab | >=8.4.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-6788 has a severity rating that is categorized as medium due to its potential for information disclosure.
To fix CVE-2019-6788, upgrade GitLab to version 11.5.8, 11.6.6, or 11.7.1 or later.
CVE-2019-6788 affects GitLab Community and Enterprise Editions prior to the specified patched versions.
The impact of CVE-2019-6788 is the potential unauthorized access to sensitive user information due to a covert redirect in OAuth integrations.
You can identify if your GitLab installation is affected by CVE-2019-6788 by checking the version number of your GitLab software.