CVE-2018-20498: Medium severity gitlab vulnerability
Published Dec 30, 2019
·Updated
An issue was discovered in GitLab Community and Enterprise Edition before 11.4.13, 11.5.x before 11.5.6, and 11.6.x before 11.6.1. It has Incorrect Access Control.
Affected Software
6 affected components
GitLab GitLab>=8.10.0<11.4.13
GitLab GitLab>=8.10.0<11.4.13
GitLab GitLab>=11.5.0<11.5.6
GitLab GitLab>=11.5.0<11.5.6
GitLab GitLab>=11.6.0<11.6.1
GitLab GitLab>=11.6.0<11.6.1
Event History
Dec 30, 2019
CVE Published
via MITRE·09:24 PM
Data Sourced
via MITRE·09:24 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2018-20498?
CVE-2018-20498 is classified as a high severity vulnerability due to incorrect access control allowing unauthorized actions.
2
How do I fix CVE-2018-20498?
To fix CVE-2018-20498, upgrade your GitLab installation to version 11.4.13, 11.5.6, or 11.6.1 or later.
3
What versions of GitLab are affected by CVE-2018-20498?
CVE-2018-20498 affects GitLab Community and Enterprise Editions before versions 11.4.13, 11.5.6, and 11.6.1.
4
What type of issue is CVE-2018-20498?
CVE-2018-20498 pertains to an issue of incorrect access control in GitLab.
5
Is there a risk of data exposure with CVE-2018-20498?
Yes, CVE-2018-20498 poses a risk of potential data exposure due to unauthorized access to restricted functionalities.