CVE-2018-20489: 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>=9.1.0<11.4.13
GitLab GitLab>=9.1.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
Remediation
Patch Available
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-20489?
CVE-2018-20489 has been classified as a high severity vulnerability due to its potential impact on user data and access control.
2
How do I fix CVE-2018-20489?
To fix CVE-2018-20489, upgrade to GitLab Community and Enterprise Editions 11.4.13, 11.5.6, or 11.6.1 or later.
3
What type of vulnerability is CVE-2018-20489?
CVE-2018-20489 is categorized as an Incorrect Access Control vulnerability.
4
Which versions of GitLab are affected by CVE-2018-20489?
CVE-2018-20489 affects GitLab Community and Enterprise Editions prior to versions 11.4.13, 11.5.6, and 11.6.1.
5
Is CVE-2018-20489 related to user permissions in GitLab?
Yes, CVE-2018-20489 involves incorrect access control, which can lead to unauthorized user access in GitLab.