What is the severity of CVE-2018-20229?

CVE-2018-20229 is classified as a critical vulnerability due to its potential for directory traversal attacks.

How do I fix CVE-2018-20229?

To resolve CVE-2018-20229, you should update to GitLab versions 11.3.14, 11.4.12, or 11.5.5 or later.

What versions of GitLab are affected by CVE-2018-20229?

CVE-2018-20229 affects GitLab Community and Enterprise Editions prior to versions 11.3.14, 11.4.12, and 11.5.5.

What kind of attack does CVE-2018-20229 facilitate?

CVE-2018-20229 allows for directory traversal attacks, which can expose sensitive files on the server.

Is CVE-2018-20229 a known vulnerability?

Yes, CVE-2018-20229 is a publicly known vulnerability that has been documented and reported.

Vulnerability/
CVE-2018-20229

high

7.5

CWE

4/4/2019

5/8/2024

CVE-2018-20229: Path Traversal

First published: Thu Apr 04 2019(Updated: )

GitLab Community and Enterprise Edition before 11.3.14, 11.4.x before 11.4.12, and 11.5.x before 11.5.5 allows Directory Traversal.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	<11.3.14
GitLab	<11.3.14
GitLab	>=11.4.0<11.4.12
GitLab	>=11.4.0<11.4.12
GitLab	>=11.5.0<11.5.5
GitLab	>=11.5.0<11.5.5

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-20229?
CVE-2018-20229 is classified as a critical vulnerability due to its potential for directory traversal attacks.
How do I fix CVE-2018-20229?
To resolve CVE-2018-20229, you should update to GitLab versions 11.3.14, 11.4.12, or 11.5.5 or later.
What versions of GitLab are affected by CVE-2018-20229?
CVE-2018-20229 affects GitLab Community and Enterprise Editions prior to versions 11.3.14, 11.4.12, and 11.5.5.
What kind of attack does CVE-2018-20229 facilitate?
CVE-2018-20229 allows for directory traversal attacks, which can expose sensitive files on the server.
Is CVE-2018-20229 a known vulnerability?
Yes, CVE-2018-20229 is a publicly known vulnerability that has been documented and reported.

agent/references
agent/type
agent/weakness
agent/author
agent/severity
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.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-20229?
CVE-2018-20229 is classified as a critical vulnerability due to its potential for directory traversal attacks.
How do I fix CVE-2018-20229?
To resolve CVE-2018-20229, you should update to GitLab versions 11.3.14, 11.4.12, or 11.5.5 or later.
What versions of GitLab are affected by CVE-2018-20229?
CVE-2018-20229 affects GitLab Community and Enterprise Editions prior to versions 11.3.14, 11.4.12, and 11.5.5.
What kind of attack does CVE-2018-20229 facilitate?
CVE-2018-20229 allows for directory traversal attacks, which can expose sensitive files on the server.
Is CVE-2018-20229 a known vulnerability?
Yes, CVE-2018-20229 is a publicly known vulnerability that has been documented and reported.