What is the severity of CVE-2017-0923?

CVE-2017-0923 is classified as a medium severity vulnerability due to its potential for persistent cross-site scripting.

How do I fix CVE-2017-0923?

To fix CVE-2017-0923, upgrade to GitLab versions 10.3.4 or later, or apply the recommended patches from GitLab.

What versions of GitLab are affected by CVE-2017-0923?

CVE-2017-0923 affects GitLab versions 9.5.10, 10.1.5, 10.2.5, and 10.3.3.

What type of attack does CVE-2017-0923 enable?

CVE-2017-0923 enables persistent cross-site scripting attacks, which can compromise user data and session information.

Is there a workaround for CVE-2017-0923?

There is no official workaround for CVE-2017-0923; the best mitigation is to update to a non-vulnerable version of GitLab.

Vulnerability/
CVE-2017-0923

medium

6.1

CWE

79 20

21/3/2018

5/8/2024

CVE-2017-0923: XSS

First published: Wed Mar 21 2018(Updated: )

Gitlab Community Edition version 9.1 is vulnerable to lack of input validation in the IPython notebooks component resulting in persistent cross site scripting.

Credit: support@hackerone.com

Affected Software	Affected Version	How to fix
GitLab	=9.5.10
GitLab	=9.5.10
GitLab	=10.1.5
GitLab	=10.1.5
GitLab	=10.2.5
GitLab	=10.2.5
GitLab	=10.3.3
GitLab	=10.3.3

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-0923?
CVE-2017-0923 is classified as a medium severity vulnerability due to its potential for persistent cross-site scripting.
How do I fix CVE-2017-0923?
To fix CVE-2017-0923, upgrade to GitLab versions 10.3.4 or later, or apply the recommended patches from GitLab.
What versions of GitLab are affected by CVE-2017-0923?
CVE-2017-0923 affects GitLab versions 9.5.10, 10.1.5, 10.2.5, and 10.3.3.
What type of attack does CVE-2017-0923 enable?
CVE-2017-0923 enables persistent cross-site scripting attacks, which can compromise user data and session information.
Is there a workaround for CVE-2017-0923?
There is no official workaround for CVE-2017-0923; the best mitigation is to update to a non-vulnerable version of GitLab.

agent/weakness
agent/references
agent/type
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/9.5.10
version/gitlab/10.1.5
version/gitlab/10.2.5
version/gitlab/10.3.3

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-0923?
CVE-2017-0923 is classified as a medium severity vulnerability due to its potential for persistent cross-site scripting.
How do I fix CVE-2017-0923?
To fix CVE-2017-0923, upgrade to GitLab versions 10.3.4 or later, or apply the recommended patches from GitLab.
What versions of GitLab are affected by CVE-2017-0923?
CVE-2017-0923 affects GitLab versions 9.5.10, 10.1.5, 10.2.5, and 10.3.3.
What type of attack does CVE-2017-0923 enable?
CVE-2017-0923 enables persistent cross-site scripting attacks, which can compromise user data and session information.
Is there a workaround for CVE-2017-0923?
There is no official workaround for CVE-2017-0923; the best mitigation is to update to a non-vulnerable version of GitLab.