CVE-2018-20144: Path Traversal
Published Mar 28, 2019
·Updated
GitLab Community and Enterprise Edition 11.x before 11.3.13, 11.4.x before 11.4.11, and 11.5.x before 11.5.4 has Incorrect Access Control.
Affected Software
6 affected components
GitLab GitLab>=11.0.0<11.3.13
GitLab GitLab>=11.0.0<11.3.13
GitLab GitLab>=11.4.0<11.4.11
GitLab GitLab>=11.4.0<11.4.11
GitLab GitLab>=11.5.0<11.5.4
GitLab GitLab>=11.5.0<11.5.4
Event History
Mar 28, 2019
CVE Published
via MITRE·02:53 PM
Data Sourced
via MITRE·02:53 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2018-20144?
CVE-2018-20144 is classified as a high severity vulnerability due to incorrect access control in GitLab.
2
How do I fix CVE-2018-20144?
To fix CVE-2018-20144, upgrade GitLab to the latest version available beyond 11.3.13, 11.4.11, or 11.5.4.
3
What versions of GitLab are affected by CVE-2018-20144?
CVE-2018-20144 affects GitLab Community and Enterprise Editions 11.0.0 to below 11.3.13, 11.4.0 to below 11.4.11, and 11.5.0 to below 11.5.4.
4
What are the implications of CVE-2018-20144?
The implications of CVE-2018-20144 include potential unauthorized access to sensitive data and actions by unauthorized users.
5
Is CVE-2018-20144 fixed in the latest GitLab releases?
Yes, CVE-2018-20144 is resolved in GitLab versions released after 11.3.13, 11.4.11, and 11.5.4.