What is the severity of CVE-2019-9179?

The severity of CVE-2019-9179 is classified as medium, indicating a moderate risk of information exposure.

How do I fix CVE-2019-9179?

To fix CVE-2019-9179, users should upgrade to GitLab Community or Enterprise Edition version 11.6.10, 11.7.6, or 11.8.1 or later.

What does CVE-2019-9179 affect?

CVE-2019-9179 affects various versions of GitLab Community and Enterprise Editions prior to specific patched versions.

What type of vulnerability is CVE-2019-9179?

CVE-2019-9179 is categorized as an Information Exposure vulnerability.

When was CVE-2019-9179 disclosed?

CVE-2019-9179 was disclosed in March 2019, affecting multiple earlier versions of GitLab.

Vulnerability/
CVE-2019-9179

medium

4.3

CWE

200

17/4/2019

21/11/2024

CVE-2019-9179: Infoleak

First published: Wed Apr 17 2019(Updated: )

An issue was discovered in GitLab Community and Enterprise Edition before 11.6.10, 11.7.x before 11.7.6, and 11.8.x before 11.8.1. It allows Information Exposure (issue 5 of 5).

Credit: cve@mitre.org cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	<11.6.10
GitLab	<11.6.10
GitLab	>=11.7.0<11.7.6
GitLab	>=11.7.0<11.7.6
GitLab	>=11.8.0<11.8.1
GitLab	>=11.8.0<11.8.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-9179?
The severity of CVE-2019-9179 is classified as medium, indicating a moderate risk of information exposure.
How do I fix CVE-2019-9179?
To fix CVE-2019-9179, users should upgrade to GitLab Community or Enterprise Edition version 11.6.10, 11.7.6, or 11.8.1 or later.
What does CVE-2019-9179 affect?
CVE-2019-9179 affects various versions of GitLab Community and Enterprise Editions prior to specific patched versions.
What type of vulnerability is CVE-2019-9179?
CVE-2019-9179 is categorized as an Information Exposure vulnerability.
When was CVE-2019-9179 disclosed?
CVE-2019-9179 was disclosed in March 2019, affecting multiple earlier versions of GitLab.

agent/type
agent/references
agent/weakness
agent/severity
agent/description
collector/mitre-cve
source/MITRE
agent/first-publish-date
agent/last-modified-date
agent/author
agent/softwarecombine
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.7.0
version/gitlab/11.8.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-9179?
The severity of CVE-2019-9179 is classified as medium, indicating a moderate risk of information exposure.
How do I fix CVE-2019-9179?
To fix CVE-2019-9179, users should upgrade to GitLab Community or Enterprise Edition version 11.6.10, 11.7.6, or 11.8.1 or later.
What does CVE-2019-9179 affect?
CVE-2019-9179 affects various versions of GitLab Community and Enterprise Editions prior to specific patched versions.
What type of vulnerability is CVE-2019-9179?
CVE-2019-9179 is categorized as an Information Exposure vulnerability.
When was CVE-2019-9179 disclosed?
CVE-2019-9179 was disclosed in March 2019, affecting multiple earlier versions of GitLab.