What is the severity of CVE-2017-0917?

CVE-2017-0917 has a medium severity rating due to its potential for persistent cross-site scripting attacks.

How do I fix CVE-2017-0917?

To fix CVE-2017-0917, upgrade your GitLab installation to version 10.2.5 or later.

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

CVE-2017-0917 affects GitLab versions between 10.1.0 and 10.2.4.

Is CVE-2017-0917 specific to GitLab Community Edition?

CVE-2017-0917 affects both the GitLab Community and Enterprise editions.

What impact does CVE-2017-0917 have on users?

CVE-2017-0917 allows attackers to inject malicious scripts that can affect users who interact with the compromised CI job component.

Vulnerability/
CVE-2017-0917

medium

6.1

CWE

20 79

21/3/2018

5/8/2024

CVE-2017-0917: Input Validation

First published: Wed Mar 21 2018(Updated: )

Gitlab Community Edition version 10.2.4 is vulnerable to lack of input validation in the CI job component resulting in persistent cross site scripting.

Credit: support@hackerone.com

Affected Software	Affected Version	How to fix
debian/gitlab		16.0.8+ds1-2
GitLab	>=10.1.0<=10.1.5
GitLab	>=10.1.0<=10.1.5
GitLab	>=10.2.0<=10.2.5
GitLab	>=10.2.0<=10.2.5
GitLab	>=10.3.0<=10.3.3
GitLab	>=10.3.0<=10.3.3
Debian Debian Linux	=9.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-0917?
CVE-2017-0917 has a medium severity rating due to its potential for persistent cross-site scripting attacks.
How do I fix CVE-2017-0917?
To fix CVE-2017-0917, upgrade your GitLab installation to version 10.2.5 or later.
Which versions of GitLab are affected by CVE-2017-0917?
CVE-2017-0917 affects GitLab versions between 10.1.0 and 10.2.4.
Is CVE-2017-0917 specific to GitLab Community Edition?
CVE-2017-0917 affects both the GitLab Community and Enterprise editions.
What impact does CVE-2017-0917 have on users?
CVE-2017-0917 allows attackers to inject malicious scripts that can affect users who interact with the compromised CI job component.

collector/security-tracker-debian
agent/references
agent/type
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
package-manager/debian
vendor/gitlab
canonical/gitlab
version/gitlab/10.1.0
version/gitlab/10.1.5
version/gitlab/10.2.0
version/gitlab/10.2.5
version/gitlab/10.3.0
version/gitlab/10.3.3
vendor/debian
canonical/debian debian linux
version/debian debian linux/9.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-2017-0917?
CVE-2017-0917 has a medium severity rating due to its potential for persistent cross-site scripting attacks.
How do I fix CVE-2017-0917?
To fix CVE-2017-0917, upgrade your GitLab installation to version 10.2.5 or later.
Which versions of GitLab are affected by CVE-2017-0917?
CVE-2017-0917 affects GitLab versions between 10.1.0 and 10.2.4.
Is CVE-2017-0917 specific to GitLab Community Edition?
CVE-2017-0917 affects both the GitLab Community and Enterprise editions.
What impact does CVE-2017-0917 have on users?
CVE-2017-0917 allows attackers to inject malicious scripts that can affect users who interact with the compromised CI job component.