What is the severity of CVE-2019-5466?

CVE-2019-5466 is considered a Medium severity vulnerability due to its potential to expose sensitive label names through an IDOR issue.

How do I fix CVE-2019-5466?

To fix CVE-2019-5466, upgrade GitLab to version 12.1.2 or later, as this version contains the necessary security patches.

What impact does CVE-2019-5466 have on GitLab?

CVE-2019-5466 allows attackers to view label names of merge requests which may lead to information disclosure in GitLab instances.

Is CVE-2019-5466 present in older versions of GitLab?

Yes, CVE-2019-5466 affects GitLab CE/EE versions 11.5.0 to 11.11.7.

Can CVE-2019-5466 be exploited remotely?

Yes, CVE-2019-5466 can be exploited remotely by authenticated users to access unauthorized label information.

Vulnerability/
CVE-2019-5466

medium

4.3

CWE

639

28/1/2020

4/8/2024

CVE-2019-5466

First published: Tue Jan 28 2020(Updated: )

An IDOR was discovered in GitLab CE/EE 11.5 and later that allowed new merge requests endpoint to disclose label names.

Credit: support@hackerone.com

Affected Software	Affected Version	How to fix
GitLab	>=11.5.0<11.11.7
GitLab	>=11.5.0<11.11.7

Remedy

https://about.gitlab.com/releases/2019/07/29/security-release-gitlab-12-dot-1-dot-2-released/

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-5466?
CVE-2019-5466 is considered a Medium severity vulnerability due to its potential to expose sensitive label names through an IDOR issue.
How do I fix CVE-2019-5466?
To fix CVE-2019-5466, upgrade GitLab to version 12.1.2 or later, as this version contains the necessary security patches.
What impact does CVE-2019-5466 have on GitLab?
CVE-2019-5466 allows attackers to view label names of merge requests which may lead to information disclosure in GitLab instances.
Is CVE-2019-5466 present in older versions of GitLab?
Yes, CVE-2019-5466 affects GitLab CE/EE versions 11.5.0 to 11.11.7.
Can CVE-2019-5466 be exploited remotely?
Yes, CVE-2019-5466 can be exploited remotely by authenticated users to access unauthorized label information.

agent/type
agent/references
agent/remedy
agent/severity
agent/weakness
agent/author
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/11.5.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-5466?
CVE-2019-5466 is considered a Medium severity vulnerability due to its potential to expose sensitive label names through an IDOR issue.
How do I fix CVE-2019-5466?
To fix CVE-2019-5466, upgrade GitLab to version 12.1.2 or later, as this version contains the necessary security patches.
What impact does CVE-2019-5466 have on GitLab?
CVE-2019-5466 allows attackers to view label names of merge requests which may lead to information disclosure in GitLab instances.
Is CVE-2019-5466 present in older versions of GitLab?
Yes, CVE-2019-5466 affects GitLab CE/EE versions 11.5.0 to 11.11.7.
Can CVE-2019-5466 be exploited remotely?
Yes, CVE-2019-5466 can be exploited remotely by authenticated users to access unauthorized label information.