What is the severity of CVE-2018-19579?

CVE-2018-19579 is classified with a high severity due to its potential for persistent XSS attacks.

How do I fix CVE-2018-19579?

To remediate CVE-2018-19579, upgrade GitLab EE to version 11.5.1 or later.

What specific version of GitLab EE is affected by CVE-2018-19579?

GitLab EE version 11.5.0 is affected by CVE-2018-19579.

What type of vulnerability is CVE-2018-19579?

CVE-2018-19579 is a persistent cross-site scripting (XSS) vulnerability.

Where is the vulnerability in CVE-2018-19579 found?

The vulnerability in CVE-2018-19579 is located on the Operations page of GitLab EE.

Vulnerability/
CVE-2018-19579

medium

5.4

CWE

10/7/2019

5/8/2024

CVE-2018-19579: XSS

First published: Wed Jul 10 2019(Updated: )

GitLab EE version 11.5 is vulnerable to a persistent XSS vulnerability in the Operations page. This is fixed in 11.5.1.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=11.5.0<11.5.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-19579?
CVE-2018-19579 is classified with a high severity due to its potential for persistent XSS attacks.
How do I fix CVE-2018-19579?
To remediate CVE-2018-19579, upgrade GitLab EE to version 11.5.1 or later.
What specific version of GitLab EE is affected by CVE-2018-19579?
GitLab EE version 11.5.0 is affected by CVE-2018-19579.
What type of vulnerability is CVE-2018-19579?
CVE-2018-19579 is a persistent cross-site scripting (XSS) vulnerability.
Where is the vulnerability in CVE-2018-19579 found?
The vulnerability in CVE-2018-19579 is located on the Operations page of GitLab EE.

agent/references
agent/type
agent/weakness
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/11.5.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-19579?
CVE-2018-19579 is classified with a high severity due to its potential for persistent XSS attacks.
How do I fix CVE-2018-19579?
To remediate CVE-2018-19579, upgrade GitLab EE to version 11.5.1 or later.
What specific version of GitLab EE is affected by CVE-2018-19579?
GitLab EE version 11.5.0 is affected by CVE-2018-19579.
What type of vulnerability is CVE-2018-19579?
CVE-2018-19579 is a persistent cross-site scripting (XSS) vulnerability.
Where is the vulnerability in CVE-2018-19579 found?
The vulnerability in CVE-2018-19579 is located on the Operations page of GitLab EE.