What is the severity of CVE-2018-19577?

CVE-2018-19577 is classified as a medium severity vulnerability due to its potential impact on sensitive issue visibility.

How do I fix CVE-2018-19577?

To remediate CVE-2018-19577, upgrade GitLab to version 11.3.11 or later for the affected versions.

What versions are affected by CVE-2018-19577?

CVE-2018-19577 affects GitLab CE/EE versions from 8.6 up to but not including 11.3.11, 11.4 before 11.4.8, and 11.5 before 11.5.1.

What does CVE-2018-19577 exploit?

CVE-2018-19577 exploits an incorrect access control vulnerability that allows unauthorized users to see the title and namespace of confidential issues.

How can I determine if my GitLab instance is vulnerable to CVE-2018-19577?

You can determine vulnerability to CVE-2018-19577 by checking if your GitLab version is within the affected version range listed above.

Vulnerability/
CVE-2018-19577

medium

5.3

CWE

284

10/7/2019

5/8/2024

CVE-2018-19577

First published: Wed Jul 10 2019(Updated: )

Gitlab CE/EE, versions 8.6 up to 11.x before 11.3.11, 11.4 before 11.4.8, and 11.5 before 11.5.1, are vulnerable to an incorrect access control vulnerability that displays to an unauthorized user the title and namespace of a confidential issue.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=8.6.0<11.3.11
GitLab	>=8.6.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-19577?
CVE-2018-19577 is classified as a medium severity vulnerability due to its potential impact on sensitive issue visibility.
How do I fix CVE-2018-19577?
To remediate CVE-2018-19577, upgrade GitLab to version 11.3.11 or later for the affected versions.
What versions are affected by CVE-2018-19577?
CVE-2018-19577 affects GitLab CE/EE versions from 8.6 up to but not including 11.3.11, 11.4 before 11.4.8, and 11.5 before 11.5.1.
What does CVE-2018-19577 exploit?
CVE-2018-19577 exploits an incorrect access control vulnerability that allows unauthorized users to see the title and namespace of confidential issues.
How can I determine if my GitLab instance is vulnerable to CVE-2018-19577?
You can determine vulnerability to CVE-2018-19577 by checking if your GitLab version is within the affected version range listed above.

agent/type
agent/references
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/8.6.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-19577?
CVE-2018-19577 is classified as a medium severity vulnerability due to its potential impact on sensitive issue visibility.
How do I fix CVE-2018-19577?
To remediate CVE-2018-19577, upgrade GitLab to version 11.3.11 or later for the affected versions.
What versions are affected by CVE-2018-19577?
CVE-2018-19577 affects GitLab CE/EE versions from 8.6 up to but not including 11.3.11, 11.4 before 11.4.8, and 11.5 before 11.5.1.
What does CVE-2018-19577 exploit?
CVE-2018-19577 exploits an incorrect access control vulnerability that allows unauthorized users to see the title and namespace of confidential issues.
How can I determine if my GitLab instance is vulnerable to CVE-2018-19577?
You can determine vulnerability to CVE-2018-19577 by checking if your GitLab version is within the affected version range listed above.