What is the severity of CVE-2018-18644?

The severity of CVE-2018-18644 is classified as a medium risk due to the potential for information exposure.

How do I fix CVE-2018-18644?

To fix CVE-2018-18644, upgrade to GitLab versions 11.2.7, 11.3.8, or 11.4.3 or later.

What are the affected versions in CVE-2018-18644?

CVE-2018-18644 affects GitLab Community and Enterprise Edition versions before 11.2.7, 11.3.8, and 11.4.3.

What type of vulnerability is CVE-2018-18644?

CVE-2018-18644 is classified as an Information Exposure vulnerability via GitLab's Prometheus integration.

How can I identify if I am affected by CVE-2018-18644?

You can identify if you are affected by CVE-2018-18644 by checking if your GitLab version is older than the specified patched versions.

Vulnerability/
CVE-2018-18644

medium

6.5

CWE

200

4/12/2018

5/8/2024

CVE-2018-18644: Infoleak

First published: Tue Dec 04 2018(Updated: )

An issue was discovered in GitLab Community and Enterprise Edition 11.x before 11.2.7, 11.3.x before 11.3.8, and 11.4.x before 11.4.3. It allows Information Exposure via a Gitlab Prometheus integration.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=11.2.0<11.2.7
GitLab	>=11.2.0<11.2.7
GitLab	>=11.3.0<11.3.8
GitLab	>=11.3.0<11.3.8
GitLab	>=11.4.0<11.4.3
GitLab	>=11.4.0<11.4.3

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-18644?
The severity of CVE-2018-18644 is classified as a medium risk due to the potential for information exposure.
How do I fix CVE-2018-18644?
To fix CVE-2018-18644, upgrade to GitLab versions 11.2.7, 11.3.8, or 11.4.3 or later.
What are the affected versions in CVE-2018-18644?
CVE-2018-18644 affects GitLab Community and Enterprise Edition versions before 11.2.7, 11.3.8, and 11.4.3.
What type of vulnerability is CVE-2018-18644?
CVE-2018-18644 is classified as an Information Exposure vulnerability via GitLab's Prometheus integration.
How can I identify if I am affected by CVE-2018-18644?
You can identify if you are affected by CVE-2018-18644 by checking if your GitLab version is older than the specified patched versions.

agent/references
agent/type
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/11.2.0
version/gitlab/11.3.0
version/gitlab/11.4.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-18644?
The severity of CVE-2018-18644 is classified as a medium risk due to the potential for information exposure.
How do I fix CVE-2018-18644?
To fix CVE-2018-18644, upgrade to GitLab versions 11.2.7, 11.3.8, or 11.4.3 or later.
What are the affected versions in CVE-2018-18644?
CVE-2018-18644 affects GitLab Community and Enterprise Edition versions before 11.2.7, 11.3.8, and 11.4.3.
What type of vulnerability is CVE-2018-18644?
CVE-2018-18644 is classified as an Information Exposure vulnerability via GitLab's Prometheus integration.
How can I identify if I am affected by CVE-2018-18644?
You can identify if you are affected by CVE-2018-18644 by checking if your GitLab version is older than the specified patched versions.