CVE-2018-20492: Medium severity gitlab vulnerability
Published Dec 26, 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 (issue 2 of 6).
Affected Software
6 affected components
GitLab GitLab>=8.0.0<11.4.13
GitLab GitLab>=8.0.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 26, 2019
CVE Published
via MITRE·04:44 PM
Data Sourced
via MITRE·04:44 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2018-20492?
CVE-2018-20492 has a medium severity rating due to its Incorrect Access Control vulnerability.
2
How do I fix CVE-2018-20492?
To fix CVE-2018-20492, upgrade GitLab to version 11.4.13 or later, 11.5.6 or later, or 11.6.1 or later.
3
Which versions of GitLab are affected by CVE-2018-20492?
CVE-2018-20492 affects GitLab Community and Enterprise Edition versions before 11.4.13, 11.5.x before 11.5.6, and 11.6.x before 11.6.1.
4
What type of vulnerability is CVE-2018-20492?
CVE-2018-20492 is classified as an Incorrect Access Control vulnerability.
5
When was CVE-2018-20492 disclosed?
CVE-2018-20492 was disclosed in December 2018 alongside the security release of GitLab.