What is the severity of CVE-2019-15580?

The severity of CVE-2019-15580 is categorized as medium.

How do I fix CVE-2019-15580?

To fix CVE-2019-15580, you should upgrade GitLab to version 12.3.3 or later.

What versions are affected by CVE-2019-15580?

CVE-2019-15580 affects GitLab versions 12.1.10 and earlier, 12.2.6 and earlier, and 12.3.2 and earlier.

What type of information is exposed in CVE-2019-15580?

CVE-2019-15580 exposes head pipeline data of public projects to unauthenticated users.

Can CVE-2019-15580 be exploited without authentication?

Yes, CVE-2019-15580 can be exploited by unauthenticated users.

Vulnerability/
CVE-2019-15580

medium

6.5

CWE

200 201

18/12/2019

5/8/2024

CVE-2019-15580: Infoleak

First published: Wed Dec 18 2019(Updated: )

An information exposure vulnerability exists in gitlab.com <v12.3.2, <v12.2.6, and <v12.1.10 when using the blocking merge request feature, it was possible for an unauthenticated user to see the head pipeline data of a public project even though pipeline visibility was restricted.

Credit: support@hackerone.com

Affected Software	Affected Version	How to fix
GitLab	<12.1.10
GitLab	<12.1.10
GitLab	>=12.2.0<12.2.6
GitLab	>=12.2.0<12.2.6
GitLab	>=12.3.0<12.3.2
GitLab	>=12.3.0<12.3.2

Never miss a vulnerability like this again

Reference Links

https://hackerone.com/reports/667408

Frequently Asked Questions

What is the severity of CVE-2019-15580?
The severity of CVE-2019-15580 is categorized as medium.
How do I fix CVE-2019-15580?
To fix CVE-2019-15580, you should upgrade GitLab to version 12.3.3 or later.
What versions are affected by CVE-2019-15580?
CVE-2019-15580 affects GitLab versions 12.1.10 and earlier, 12.2.6 and earlier, and 12.3.2 and earlier.
What type of information is exposed in CVE-2019-15580?
CVE-2019-15580 exposes head pipeline data of public projects to unauthenticated users.
Can CVE-2019-15580 be exploited without authentication?
Yes, CVE-2019-15580 can be exploited by unauthenticated users.

agent/type
agent/references
agent/author
agent/weakness
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/12.2.0
version/gitlab/12.3.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-15580?
The severity of CVE-2019-15580 is categorized as medium.
How do I fix CVE-2019-15580?
To fix CVE-2019-15580, you should upgrade GitLab to version 12.3.3 or later.
What versions are affected by CVE-2019-15580?
CVE-2019-15580 affects GitLab versions 12.1.10 and earlier, 12.2.6 and earlier, and 12.3.2 and earlier.
What type of information is exposed in CVE-2019-15580?
CVE-2019-15580 exposes head pipeline data of public projects to unauthenticated users.
Can CVE-2019-15580 be exploited without authentication?
Yes, CVE-2019-15580 can be exploited by unauthenticated users.