What is the severity of CVE-2019-11545?

CVE-2019-11545 is considered a medium severity vulnerability due to its potential for information disclosure.

How do I fix CVE-2019-11545?

To fix CVE-2019-11545, update GitLab to version 11.9.10 or 11.10.2 or later.

What type of vulnerability is CVE-2019-11545?

CVE-2019-11545 is categorized as an Information Disclosure vulnerability.

Who is affected by CVE-2019-11545?

CVE-2019-11545 affects users of GitLab Community Edition and Enterprise Edition versions before 11.9.10 and 11.10.2.

What happens if CVE-2019-11545 is exploited?

Exploitation of CVE-2019-11545 can lead to unauthorized users gaining access to private project namespaces.

Vulnerability/
CVE-2019-11545

medium

4.3

CWE

200

9/9/2019

4/8/2024

CVE-2019-11545: Infoleak

First published: Mon Sep 09 2019(Updated: )

An issue was discovered in GitLab Community Edition 11.9.x before 11.9.10 and 11.10.x before 11.10.2. It allows Information Disclosure. When an issue is moved to a private project, the private project namespace is leaked to unauthorized users with access to the original issue.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=11.9.0<11.9.10
GitLab	>=11.9.0<11.9.10
GitLab	>=11.10.0<11.10.2
GitLab	>=11.10.0<11.10.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-11545?
CVE-2019-11545 is considered a medium severity vulnerability due to its potential for information disclosure.
How do I fix CVE-2019-11545?
To fix CVE-2019-11545, update GitLab to version 11.9.10 or 11.10.2 or later.
What type of vulnerability is CVE-2019-11545?
CVE-2019-11545 is categorized as an Information Disclosure vulnerability.
Who is affected by CVE-2019-11545?
CVE-2019-11545 affects users of GitLab Community Edition and Enterprise Edition versions before 11.9.10 and 11.10.2.
What happens if CVE-2019-11545 is exploited?
Exploitation of CVE-2019-11545 can lead to unauthorized users gaining access to private project namespaces.

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.9.0
version/gitlab/11.10.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-11545?
CVE-2019-11545 is considered a medium severity vulnerability due to its potential for information disclosure.
How do I fix CVE-2019-11545?
To fix CVE-2019-11545, update GitLab to version 11.9.10 or 11.10.2 or later.
What type of vulnerability is CVE-2019-11545?
CVE-2019-11545 is categorized as an Information Disclosure vulnerability.
Who is affected by CVE-2019-11545?
CVE-2019-11545 affects users of GitLab Community Edition and Enterprise Edition versions before 11.9.10 and 11.10.2.
What happens if CVE-2019-11545 is exploited?
Exploitation of CVE-2019-11545 can lead to unauthorized users gaining access to private project namespaces.