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.

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.

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.

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.

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.

Vulnerability/
CVE-2018-20144

high

7.5

CWE

28/3/2019

5/8/2024

CVE-2018-20144: Path Traversal

First published: Thu 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.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=11.0.0<11.3.13
GitLab	>=11.0.0<11.3.13
GitLab	>=11.4.0<11.4.11
GitLab	>=11.4.0<11.4.11
GitLab	>=11.5.0<11.5.4
GitLab	>=11.5.0<11.5.4

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

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.
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.
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.
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.
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.

agent/type
agent/references
agent/severity
agent/weakness
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/11.0.0
version/gitlab/11.4.0
version/gitlab/11.5.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

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.
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.
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.
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.
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.