What is the severity of CVE-2019-13001?

CVE-2019-13001 is classified as a medium severity vulnerability due to its potential to allow unauthorized modification of private snippets.

How do I fix CVE-2019-13001?

To fix CVE-2019-13001, you should upgrade GitLab to version 12.0.3 or later, as the vulnerability has been addressed in these releases.

What impact does CVE-2019-13001 have on my GitLab instance?

CVE-2019-13001 allows unauthorized users to add comments to private snippets, compromising the data integrity of private records.

Which versions of GitLab are affected by CVE-2019-13001?

CVE-2019-13001 affects GitLab Community and Enterprise Editions from version 11.9.0 to 12.0.2.

Is authentication required to exploit CVE-2019-13001?

No, CVE-2019-13001 does not require proper authentication, allowing unauthorized access to affected snippets.

Vulnerability/
CVE-2019-13001

medium

4.3

CWE

863

10/3/2020

4/8/2024

CVE-2019-13001

First published: Tue Mar 10 2020(Updated: )

An issue was discovered in GitLab Community and Enterprise Edition 11.9 and later through 12.0.2. GitLab Snippets were vulnerable to an authorization issue that allowed unauthorized users to add comments to a private snippet. It allows authentication bypass.

Credit: cve@mitre.org

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

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-13001?
CVE-2019-13001 is classified as a medium severity vulnerability due to its potential to allow unauthorized modification of private snippets.
How do I fix CVE-2019-13001?
To fix CVE-2019-13001, you should upgrade GitLab to version 12.0.3 or later, as the vulnerability has been addressed in these releases.
What impact does CVE-2019-13001 have on my GitLab instance?
CVE-2019-13001 allows unauthorized users to add comments to private snippets, compromising the data integrity of private records.
Which versions of GitLab are affected by CVE-2019-13001?
CVE-2019-13001 affects GitLab Community and Enterprise Editions from version 11.9.0 to 12.0.2.
Is authentication required to exploit CVE-2019-13001?
No, CVE-2019-13001 does not require proper authentication, allowing unauthorized access to affected snippets.

agent/references
agent/type
agent/author
agent/weakness
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.9.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-13001?
CVE-2019-13001 is classified as a medium severity vulnerability due to its potential to allow unauthorized modification of private snippets.
How do I fix CVE-2019-13001?
To fix CVE-2019-13001, you should upgrade GitLab to version 12.0.3 or later, as the vulnerability has been addressed in these releases.
What impact does CVE-2019-13001 have on my GitLab instance?
CVE-2019-13001 allows unauthorized users to add comments to private snippets, compromising the data integrity of private records.
Which versions of GitLab are affected by CVE-2019-13001?
CVE-2019-13001 affects GitLab Community and Enterprise Editions from version 11.9.0 to 12.0.2.
Is authentication required to exploit CVE-2019-13001?
No, CVE-2019-13001 does not require proper authentication, allowing unauthorized access to affected snippets.