What is the severity of CVE-2019-15592?

CVE-2019-15592 is classified as a medium severity vulnerability that allows unauthorized information disclosure.

How do I fix CVE-2019-15592?

To fix CVE-2019-15592, you should upgrade your GitLab instance to version 12.2.3 or above.

Who is affected by CVE-2019-15592?

CVE-2019-15592 affects all GitLab versions up to and including 12.2.2 for both community and enterprise editions.

What type of vulnerability is CVE-2019-15592?

CVE-2019-15592 is an information disclosure vulnerability that allows guest users to see sensitive merge request IDs.

Can guest users in private projects access merge request IDs due to CVE-2019-15592?

Yes, guest users in private projects can access merge request IDs due to the vulnerability in CVE-2019-15592.

Vulnerability/
CVE-2019-15592

medium

4.3

CWE

200

14/2/2020

5/8/2024

CVE-2019-15592: Infoleak

First published: Fri Feb 14 2020(Updated: )

GitLab 12.2.2 and below contains a security vulnerability that allows a guest user in a private project to see the merge request ID associated to an issue via the activity timeline.

Credit: support@hackerone.com support@hackerone.com

Affected Software	Affected Version	How to fix
GitLab	>=11.2.0<12.0.8
GitLab	>=11.2.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
GitLab

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-15592?
CVE-2019-15592 is classified as a medium severity vulnerability that allows unauthorized information disclosure.
How do I fix CVE-2019-15592?
To fix CVE-2019-15592, you should upgrade your GitLab instance to version 12.2.3 or above.
Who is affected by CVE-2019-15592?
CVE-2019-15592 affects all GitLab versions up to and including 12.2.2 for both community and enterprise editions.
What type of vulnerability is CVE-2019-15592?
CVE-2019-15592 is an information disclosure vulnerability that allows guest users to see sensitive merge request IDs.
Can guest users in private projects access merge request IDs due to CVE-2019-15592?
Yes, guest users in private projects can access merge request IDs due to the vulnerability in CVE-2019-15592.

agent/references
agent/type
agent/author
agent/severity
agent/weakness
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-api
source/NVD
agent/software-canonical-lookup
agent/software-canonical-lookup-request
collector/nvd-index
vendor/gitlab
canonical/gitlab
version/gitlab/11.2.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-15592?
CVE-2019-15592 is classified as a medium severity vulnerability that allows unauthorized information disclosure.
How do I fix CVE-2019-15592?
To fix CVE-2019-15592, you should upgrade your GitLab instance to version 12.2.3 or above.
Who is affected by CVE-2019-15592?
CVE-2019-15592 affects all GitLab versions up to and including 12.2.2 for both community and enterprise editions.
What type of vulnerability is CVE-2019-15592?
CVE-2019-15592 is an information disclosure vulnerability that allows guest users to see sensitive merge request IDs.
Can guest users in private projects access merge request IDs due to CVE-2019-15592?
Yes, guest users in private projects can access merge request IDs due to the vulnerability in CVE-2019-15592.