What is the severity of CVE-2019-5463?

The severity of CVE-2019-5463 is classified as a medium risk due to its potential for unauthorized disclosure of build status.

How do I fix CVE-2019-5463?

To fix CVE-2019-5463, you should upgrade GitLab to version 12.1.2, 12.0.4, or 11.11.6 or later.

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

CVE-2019-5463 affects GitLab versions 11.11.0 to 11.11.6, 12.0.0 to 12.0.4, and 12.1.0 to 12.1.2.

What type of vulnerability is CVE-2019-5463?

CVE-2019-5463 is an authorization issue that can lead to unauthorized disclosure of information.

Is CVE-2019-5463 applicable to both GitLab CE and EE?

Yes, CVE-2019-5463 affects both GitLab Community Edition (CE) and Enterprise Edition (EE).

Vulnerability/
CVE-2019-5463

medium

5.3

CWE

200 862

9/9/2019

4/8/2024

CVE-2019-5463: Infoleak

First published: Mon Sep 09 2019(Updated: )

An authorization issue was discovered in the GitLab CE/EE CI badge images endpoint which could result in disclosure of the build status. This vulnerability was addressed in 12.1.2, 12.0.4, and 11.11.6.

Credit: support@hackerone.com

Affected Software	Affected Version	How to fix
GitLab	>=11.11.0<11.11.7
GitLab	>=11.11.0<11.11.7
GitLab	>=12.0.0<12.0.4
GitLab	>=12.0.0<12.0.4
GitLab	>=12.1.0<12.1.2
GitLab	>=12.1.0<12.1.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-5463?
The severity of CVE-2019-5463 is classified as a medium risk due to its potential for unauthorized disclosure of build status.
How do I fix CVE-2019-5463?
To fix CVE-2019-5463, you should upgrade GitLab to version 12.1.2, 12.0.4, or 11.11.6 or later.
Which versions of GitLab are affected by CVE-2019-5463?
CVE-2019-5463 affects GitLab versions 11.11.0 to 11.11.6, 12.0.0 to 12.0.4, and 12.1.0 to 12.1.2.
What type of vulnerability is CVE-2019-5463?
CVE-2019-5463 is an authorization issue that can lead to unauthorized disclosure of information.
Is CVE-2019-5463 applicable to both GitLab CE and EE?
Yes, CVE-2019-5463 affects both GitLab Community Edition (CE) and Enterprise Edition (EE).

agent/references
agent/type
agent/weakness
agent/author
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/11.11.0
version/gitlab/12.0.0
version/gitlab/12.1.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-5463?
The severity of CVE-2019-5463 is classified as a medium risk due to its potential for unauthorized disclosure of build status.
How do I fix CVE-2019-5463?
To fix CVE-2019-5463, you should upgrade GitLab to version 12.1.2, 12.0.4, or 11.11.6 or later.
Which versions of GitLab are affected by CVE-2019-5463?
CVE-2019-5463 affects GitLab versions 11.11.0 to 11.11.6, 12.0.0 to 12.0.4, and 12.1.0 to 12.1.2.
What type of vulnerability is CVE-2019-5463?
CVE-2019-5463 is an authorization issue that can lead to unauthorized disclosure of information.
Is CVE-2019-5463 applicable to both GitLab CE and EE?
Yes, CVE-2019-5463 affects both GitLab Community Edition (CE) and Enterprise Edition (EE).