CVE-2018-20501: 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.12.0<11.4.13
GitLab GitLab>=8.12.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-20501?
CVE-2018-20501 has a medium severity rating due to its incorrect access control issues.
2
How do I fix CVE-2018-20501?
To fix CVE-2018-20501, update GitLab to version 11.4.13, 11.5.6, or 11.6.1 or later.
3
What versions of GitLab are affected by CVE-2018-20501?
CVE-2018-20501 affects GitLab Community and Enterprise Editions prior to version 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-20501?
CVE-2018-20501 is classified as an access control vulnerability.
5
How can I mitigate CVE-2018-20501 if I cannot upgrade immediately?
If an immediate upgrade is not possible, consider implementing strict access controls and monitoring to mitigate the risks associated with CVE-2018-20501.