What is the severity of CVE-2018-14605?

CVE-2018-14605 has been classified as a medium severity vulnerability due to its potential for XSS attacks.

How do I fix CVE-2018-14605?

To fix CVE-2018-14605, upgrade your GitLab installation to version 10.8.7, 11.0.5, or 11.1.2 or later.

Who is affected by CVE-2018-14605?

CVE-2018-14605 affects GitLab Community and Enterprise Editions before versions 10.8.7, 11.0.5, and 11.1.2.

What are the implications of exploiting CVE-2018-14605?

Exploiting CVE-2018-14605 may allow an attacker to execute arbitrary scripts in the context of the user's session.

Is there a workaround for CVE-2018-14605 if I can't upgrade?

There are no official workarounds for CVE-2018-14605, so it is strongly advised to apply the necessary updates as soon as possible.

Vulnerability/
CVE-2018-14605

medium

5.4

CWE

27/7/2018

5/8/2024

CVE-2018-14605: XSS

First published: Fri Jul 27 2018(Updated: )

An issue was discovered in GitLab Community and Enterprise Edition before 10.8.7, 11.0.x before 11.0.5, and 11.1.x before 11.1.2. XSS can occur in the branch name during a Web IDE file commit.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	<10.8.7
GitLab	<10.8.7
GitLab	>=11.0.0<11.0.5
GitLab	>=11.0.0<11.0.5
GitLab	>=11.1.0<11.1.2
GitLab	>=11.1.0<11.1.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-14605?
CVE-2018-14605 has been classified as a medium severity vulnerability due to its potential for XSS attacks.
How do I fix CVE-2018-14605?
To fix CVE-2018-14605, upgrade your GitLab installation to version 10.8.7, 11.0.5, or 11.1.2 or later.
Who is affected by CVE-2018-14605?
CVE-2018-14605 affects GitLab Community and Enterprise Editions before versions 10.8.7, 11.0.5, and 11.1.2.
What are the implications of exploiting CVE-2018-14605?
Exploiting CVE-2018-14605 may allow an attacker to execute arbitrary scripts in the context of the user's session.
Is there a workaround for CVE-2018-14605 if I can't upgrade?
There are no official workarounds for CVE-2018-14605, so it is strongly advised to apply the necessary updates as soon as possible.

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
vendor/gitlab
canonical/gitlab
version/gitlab/11.0.0
version/gitlab/11.1.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-14605?
CVE-2018-14605 has been classified as a medium severity vulnerability due to its potential for XSS attacks.
How do I fix CVE-2018-14605?
To fix CVE-2018-14605, upgrade your GitLab installation to version 10.8.7, 11.0.5, or 11.1.2 or later.
Who is affected by CVE-2018-14605?
CVE-2018-14605 affects GitLab Community and Enterprise Editions before versions 10.8.7, 11.0.5, and 11.1.2.
What are the implications of exploiting CVE-2018-14605?
Exploiting CVE-2018-14605 may allow an attacker to execute arbitrary scripts in the context of the user's session.
Is there a workaround for CVE-2018-14605 if I can't upgrade?
There are no official workarounds for CVE-2018-14605, so it is strongly advised to apply the necessary updates as soon as possible.