What is the severity of CVE-2018-17976?

CVE-2018-17976 has been classified as having a medium severity level due to the risk of information exposure.

How do I fix CVE-2018-17976?

To fix CVE-2018-17976, upgrade your GitLab Community Edition to version 11.1.8, 11.2.5, or 11.3.2 or later.

What types of systems are affected by CVE-2018-17976?

CVE-2018-17976 affects GitLab Community Edition versions prior to 11.1.8, 11.2.5, and 11.3.2.

What information is exposed due to CVE-2018-17976?

CVE-2018-17976 allows unauthorized users to view content in Epic change descriptions.

When was CVE-2018-17976 publicly disclosed?

CVE-2018-17976 was publicly disclosed on October 5, 2018.

Vulnerability/
CVE-2018-17976

medium

6.5

CWE

200

4/12/2018

5/8/2024

CVE-2018-17976: Infoleak

First published: Tue Dec 04 2018(Updated: )

An issue was discovered in GitLab Community Edition 11.x before 11.1.8, 11.2.x before 11.2.5, and 11.3.x before 11.3.2. There is Information Exposure via Epic change descriptions.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=11.0.0<11.1.8
GitLab	>=11.2.0<11.2.5
GitLab	>=11.3.0<11.3.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-17976?
CVE-2018-17976 has been classified as having a medium severity level due to the risk of information exposure.
How do I fix CVE-2018-17976?
To fix CVE-2018-17976, upgrade your GitLab Community Edition to version 11.1.8, 11.2.5, or 11.3.2 or later.
What types of systems are affected by CVE-2018-17976?
CVE-2018-17976 affects GitLab Community Edition versions prior to 11.1.8, 11.2.5, and 11.3.2.
What information is exposed due to CVE-2018-17976?
CVE-2018-17976 allows unauthorized users to view content in Epic change descriptions.
When was CVE-2018-17976 publicly disclosed?
CVE-2018-17976 was publicly disclosed on October 5, 2018.

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.2.0
version/gitlab/11.3.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-17976?
CVE-2018-17976 has been classified as having a medium severity level due to the risk of information exposure.
How do I fix CVE-2018-17976?
To fix CVE-2018-17976, upgrade your GitLab Community Edition to version 11.1.8, 11.2.5, or 11.3.2 or later.
What types of systems are affected by CVE-2018-17976?
CVE-2018-17976 affects GitLab Community Edition versions prior to 11.1.8, 11.2.5, and 11.3.2.
What information is exposed due to CVE-2018-17976?
CVE-2018-17976 allows unauthorized users to view content in Epic change descriptions.
When was CVE-2018-17976 publicly disclosed?
CVE-2018-17976 was publicly disclosed on October 5, 2018.