CVE-2018-18644: Infoleak
Published Dec 4, 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.
Affected Software
6 affected components
GitLab GitLab>=11.2.0<11.2.7
GitLab GitLab>=11.2.0<11.2.7
GitLab GitLab>=11.3.0<11.3.8
GitLab GitLab>=11.3.0<11.3.8
GitLab GitLab>=11.4.0<11.4.3
GitLab GitLab>=11.4.0<11.4.3
Event History
Dec 4, 2018
CVE Published
via MITRE·11:00 PM
Data Sourced
via MITRE·11:00 PM
Description
Frequently Asked Questions
1
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.
2
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.
3
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.
4
What type of vulnerability is CVE-2018-18644?
CVE-2018-18644 is classified as an Information Exposure vulnerability via GitLab's Prometheus integration.
5
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.