What is the severity of CVE-2019-13002?

CVE-2019-13002 is classified as a medium severity vulnerability due to its incorrect access control allowing unauthorized access to sensitive data.

How do I fix CVE-2019-13002?

To fix CVE-2019-13002, you should upgrade GitLab to version 12.0.3 or later.

What types of GitLab editions are affected by CVE-2019-13002?

CVE-2019-13002 affects both GitLab Community Edition and Enterprise Edition versions from 11.10.0 up to 12.0.2.

What information could be exposed due to CVE-2019-13002?

Due to CVE-2019-13002, unauthorized users could read pipeline information related to the last merge request.

Who is at risk from CVE-2019-13002?

Organizations using affected versions of GitLab are at risk if they have not implemented the recommended security updates.

Vulnerability/
CVE-2019-13002

medium

4.3

10/3/2020

4/8/2024

CVE-2019-13002

First published: Tue Mar 10 2020(Updated: )

An issue was discovered in GitLab Community and Enterprise Edition 11.10 through 12.0.2. Unauthorized users were able to read pipeline information of the last merge request. It has Incorrect Access Control.

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-13002?
CVE-2019-13002 is classified as a medium severity vulnerability due to its incorrect access control allowing unauthorized access to sensitive data.
How do I fix CVE-2019-13002?
To fix CVE-2019-13002, you should upgrade GitLab to version 12.0.3 or later.
What types of GitLab editions are affected by CVE-2019-13002?
CVE-2019-13002 affects both GitLab Community Edition and Enterprise Edition versions from 11.10.0 up to 12.0.2.
What information could be exposed due to CVE-2019-13002?
Due to CVE-2019-13002, unauthorized users could read pipeline information related to the last merge request.
Who is at risk from CVE-2019-13002?
Organizations using affected versions of GitLab are at risk if they have not implemented the recommended security updates.

agent/references
agent/type
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-13002?
CVE-2019-13002 is classified as a medium severity vulnerability due to its incorrect access control allowing unauthorized access to sensitive data.
How do I fix CVE-2019-13002?
To fix CVE-2019-13002, you should upgrade GitLab to version 12.0.3 or later.
What types of GitLab editions are affected by CVE-2019-13002?
CVE-2019-13002 affects both GitLab Community Edition and Enterprise Edition versions from 11.10.0 up to 12.0.2.
What information could be exposed due to CVE-2019-13002?
Due to CVE-2019-13002, unauthorized users could read pipeline information related to the last merge request.
Who is at risk from CVE-2019-13002?
Organizations using affected versions of GitLab are at risk if they have not implemented the recommended security updates.