CVE-2017-0918: Path Traversal

Published Mar 21, 2018
·
Updated

Gitlab Community Edition version 10.3 is vulnerable to a path traversal issue in the GitLab CI runner component resulting in remote code execution.

Affected Software

10 affected componentsFixes available
debian/gitlab
16.0.8+ds1-2
GitLab GitLab>=8.4.0<=9.5.10
GitLab GitLab>=8.4.0<=9.5.10
GitLab GitLab>=10.0.0<=10.1.5
GitLab GitLab>=10.0.0<=10.1.15
GitLab GitLab>10.2.0<=10.2.5
GitLab GitLab>=10.2.0<=10.2.5
GitLab GitLab>10.3.0<=10.3.3
GitLab GitLab>=10.3.0<=10.3.3
Debian Debian Linux=9.0

Event History

Mar 21, 2018
CVE Published
via MITRE·08:00 PM
Data Sourced
via MITRE·08:00 PM
DescriptionWeakness

Frequently Asked Questions

1

What is the severity of CVE-2017-0918?

CVE-2017-0918 has a high severity due to its potential for remote code execution.

2

How do I fix CVE-2017-0918?

To fix CVE-2017-0918, upgrade GitLab Community or Enterprise Edition to versions above 10.3.4.

3

What versions are affected by CVE-2017-0918?

CVE-2017-0918 affects GitLab Community and Enterprise Editions from versions 8.4.0 to 10.3.3.

4

What is the nature of the vulnerability in CVE-2017-0918?

CVE-2017-0918 is a path traversal vulnerability in the GitLab CI runner component.

5

Can CVE-2017-0918 be exploited remotely?

Yes, CVE-2017-0918 can be exploited remotely, allowing unauthorized access to execute code.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203