First published: Thu May 16 2019(Updated: )
An Information Exposure issue (issue 2 of 2) was discovered in GitLab Community and Enterprise Edition before 11.7.8, 11.8.x before 11.8.4, and 11.9.x before 11.9.2. During the OAuth authentication process, the application attempts to validate a parameter in an insecure way, potentially exposing data.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | <11.7.8 | |
GitLab | <11.7.8 | |
GitLab | >=11.8.0<11.8.4 | |
GitLab | >=11.8.0<11.8.4 | |
GitLab | >=11.9.0<11.9.2 | |
GitLab | >=11.9.0<11.9.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The CVE-2019-10114 vulnerability is considered to have a high severity due to the potential information exposure during the OAuth authentication process.
To fix CVE-2019-10114, update your GitLab installation to version 11.7.8 or later, 11.8.4 or later, or 11.9.2 or later.
CVE-2019-10114 affects GitLab Community and Enterprise Editions prior to versions 11.7.8, 11.8.4, and 11.9.2.
CVE-2019-10114 can potentially expose sensitive data during the OAuth authentication process due to improper validation of parameters.
Yes, CVE-2019-10114 is a publicly disclosed vulnerability that affects GitLab configurations.