What is the severity of CVE-2019-13004?

CVE-2019-13004 has a moderate severity level due to its impact on access control in comments.

How do I fix CVE-2019-13004?

To fix CVE-2019-13004, upgrade GitLab to version 12.0.3 or higher.

What versions of GitLab are affected by CVE-2019-13004?

CVE-2019-13004 affects GitLab Community and Enterprise Edition versions 11.10 through 12.0.2.

What is the impact of CVE-2019-13004?

The impact of CVE-2019-13004 is that comments with specific encoded characters become inaccessible to users.

Is CVE-2019-13004 an isolated issue in GitLab?

CVE-2019-13004 is part of two identified issues related to incorrect access control in GitLab.

Vulnerability/
CVE-2019-13004

medium

5.3

10/3/2020

4/8/2024

CVE-2019-13004

First published: Tue Mar 10 2020(Updated: )

An issue was discovered in GitLab Community and Enterprise Edition 11.10 through 12.0.2. When specific encoded characters were added to comments, the comments section would become inaccessible. It has Incorrect Access Control (issue 1 of 2).

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=11.10.0<=12.0.2
GitLab	>=11.10.0<=12.0.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-13004?
CVE-2019-13004 has a moderate severity level due to its impact on access control in comments.
How do I fix CVE-2019-13004?
To fix CVE-2019-13004, upgrade GitLab to version 12.0.3 or higher.
What versions of GitLab are affected by CVE-2019-13004?
CVE-2019-13004 affects GitLab Community and Enterprise Edition versions 11.10 through 12.0.2.
What is the impact of CVE-2019-13004?
The impact of CVE-2019-13004 is that comments with specific encoded characters become inaccessible to users.
Is CVE-2019-13004 an isolated issue in GitLab?
CVE-2019-13004 is part of two identified issues related to incorrect access control in GitLab.

agent/type
agent/references
agent/author
agent/severity
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/event
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/11.10.0
version/gitlab/12.0.2

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-13004?
CVE-2019-13004 has a moderate severity level due to its impact on access control in comments.
How do I fix CVE-2019-13004?
To fix CVE-2019-13004, upgrade GitLab to version 12.0.3 or higher.
What versions of GitLab are affected by CVE-2019-13004?
CVE-2019-13004 affects GitLab Community and Enterprise Edition versions 11.10 through 12.0.2.
What is the impact of CVE-2019-13004?
The impact of CVE-2019-13004 is that comments with specific encoded characters become inaccessible to users.
Is CVE-2019-13004 an isolated issue in GitLab?
CVE-2019-13004 is part of two identified issues related to incorrect access control in GitLab.