What is the severity of CVE-2019-15739?

The severity of CVE-2019-15739 is classified as a high severity vulnerability.

How do I fix CVE-2019-15739?

To fix CVE-2019-15739, upgrade GitLab to version 12.2.3 or later.

Which GitLab versions are affected by CVE-2019-15739?

CVE-2019-15739 affects GitLab Community and Enterprise Edition versions 8.1 to 12.2.1.

What type of vulnerability is CVE-2019-15739?

CVE-2019-15739 is an XSS (Cross-Site Scripting) vulnerability related to improper sanitization of Markdown.

Is user data at risk due to CVE-2019-15739?

Yes, CVE-2019-15739 can potentially expose user data to an attacker via XSS payloads.

Vulnerability/
CVE-2019-15739

medium

6.1

CWE

16/9/2019

5/8/2024

CVE-2019-15739: XSS

First published: Mon Sep 16 2019(Updated: )

An issue was discovered in GitLab Community and Enterprise Edition 8.1 through 12.2.1. Certain areas displaying Markdown were not properly sanitizing some XSS payloads.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=8.1.0<12.0.8
GitLab	>=8.1.0<12.0.8
GitLab	>=12.1.0<12.1.8
GitLab	>=12.1.0<12.1.8
GitLab	>=12.2.0<12.2.3
GitLab	>=12.2.0<12.2.3

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-15739?
The severity of CVE-2019-15739 is classified as a high severity vulnerability.
How do I fix CVE-2019-15739?
To fix CVE-2019-15739, upgrade GitLab to version 12.2.3 or later.
Which GitLab versions are affected by CVE-2019-15739?
CVE-2019-15739 affects GitLab Community and Enterprise Edition versions 8.1 to 12.2.1.
What type of vulnerability is CVE-2019-15739?
CVE-2019-15739 is an XSS (Cross-Site Scripting) vulnerability related to improper sanitization of Markdown.
Is user data at risk due to CVE-2019-15739?
Yes, CVE-2019-15739 can potentially expose user data to an attacker via XSS payloads.

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/8.1.0
version/gitlab/12.1.0
version/gitlab/12.2.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-2019-15739?
The severity of CVE-2019-15739 is classified as a high severity vulnerability.
How do I fix CVE-2019-15739?
To fix CVE-2019-15739, upgrade GitLab to version 12.2.3 or later.
Which GitLab versions are affected by CVE-2019-15739?
CVE-2019-15739 affects GitLab Community and Enterprise Edition versions 8.1 to 12.2.1.
What type of vulnerability is CVE-2019-15739?
CVE-2019-15739 is an XSS (Cross-Site Scripting) vulnerability related to improper sanitization of Markdown.
Is user data at risk due to CVE-2019-15739?
Yes, CVE-2019-15739 can potentially expose user data to an attacker via XSS payloads.