CVE-2017-0915: Input Validation

Published Mar 21, 2018
·
Updated

Gitlab Community Edition version 10.2.4 is vulnerable to a lack of input validation in the GitlabProjectsImportService resulting in remote code execution.

Affected Software

10 affected componentsFixes available
debian/gitlab
16.0.8+ds1-2
GitLab GitLab>=8.9.0<=9.5.10
GitLab GitLab>=8.9.0<=9.5.10
GitLab GitLab>=10.0.0<=10.1.5
GitLab GitLab>=10.0.0<=10.1.5
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-0915?

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

2

How do I fix CVE-2017-0915?

To fix CVE-2017-0915, update GitLab to version 10.2.5 or later.

3

Which versions of GitLab are affected by CVE-2017-0915?

CVE-2017-0915 affects GitLab versions from 8.9.0 up to 10.2.4.

4

What type of vulnerability is CVE-2017-0915?

CVE-2017-0915 is classified as an input validation vulnerability leading to remote code execution.

5

Who can exploit CVE-2017-0915?

CVE-2017-0915 can be exploited by unauthenticated attackers due to insufficient input validation in the GitLabProjectsImportService.

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