What is the severity of CVE-2018-19494?

CVE-2018-19494 is classified as a medium severity vulnerability due to its unauthorized access implications.

How do I fix CVE-2018-19494?

To fix CVE-2018-19494, you should upgrade GitLab to versions 11.3.11, 11.4.8, or 11.5.1 or later.

What kind of vulnerability is CVE-2018-19494?

CVE-2018-19494 is an access control vulnerability that allows unauthorized users to view private group names.

Which versions are affected by CVE-2018-19494?

CVE-2018-19494 affects GitLab Community and Enterprise Edition versions prior to 11.3.11, 11.4.8, and 11.5.1.

Who is impacted by CVE-2018-19494?

Users of GitLab versions prior to the fixed releases are impacted by CVE-2018-19494 if they have private groups.

Vulnerability/
CVE-2018-19494

medium

4.3

CWE

284

10/7/2019

5/8/2024

CVE-2018-19494

First published: Wed Jul 10 2019(Updated: )

An issue was discovered in GitLab Community and Enterprise Edition 11.x before 11.3.11, 11.4.x before 11.4.8, and 11.5.x before 11.5.1. There is an incorrect access vulnerability that allows an unauthorized user to view private group names.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=11.0.0<11.3.11
GitLab	>=11.0.0<11.3.11
GitLab	>=11.4.0<11.4.8
GitLab	>=11.4.0<11.4.8
GitLab	>=11.5.0<11.5.1
GitLab	>=11.5.0<11.5.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-19494?
CVE-2018-19494 is classified as a medium severity vulnerability due to its unauthorized access implications.
How do I fix CVE-2018-19494?
To fix CVE-2018-19494, you should upgrade GitLab to versions 11.3.11, 11.4.8, or 11.5.1 or later.
What kind of vulnerability is CVE-2018-19494?
CVE-2018-19494 is an access control vulnerability that allows unauthorized users to view private group names.
Which versions are affected by CVE-2018-19494?
CVE-2018-19494 affects GitLab Community and Enterprise Edition versions prior to 11.3.11, 11.4.8, and 11.5.1.
Who is impacted by CVE-2018-19494?
Users of GitLab versions prior to the fixed releases are impacted by CVE-2018-19494 if they have private groups.

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.0.0
version/gitlab/11.4.0
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-2018-19494?
CVE-2018-19494 is classified as a medium severity vulnerability due to its unauthorized access implications.
How do I fix CVE-2018-19494?
To fix CVE-2018-19494, you should upgrade GitLab to versions 11.3.11, 11.4.8, or 11.5.1 or later.
What kind of vulnerability is CVE-2018-19494?
CVE-2018-19494 is an access control vulnerability that allows unauthorized users to view private group names.
Which versions are affected by CVE-2018-19494?
CVE-2018-19494 affects GitLab Community and Enterprise Edition versions prior to 11.3.11, 11.4.8, and 11.5.1.
Who is impacted by CVE-2018-19494?
Users of GitLab versions prior to the fixed releases are impacted by CVE-2018-19494 if they have private groups.