CVE-2018-20495: Infoleak
Published Dec 30, 2019
·Updated
An issue was discovered in GitLab Community and Enterprise Edition 11.3.x and 11.4.x before 11.4.13, 11.5.x before 11.5.6, and 11.6.x before 11.6.1. It allows Information Exposure.
Affected Software
6 affected components
GitLab GitLab>=11.3.0<11.4.13
GitLab GitLab>=11.3.0<11.4.13
GitLab GitLab>=11.5.0<11.5.6
GitLab GitLab>=11.5.0<11.5.6
GitLab GitLab>=11.6.0<11.6.1
GitLab GitLab>=11.6.0<11.6.1
Event History
Dec 30, 2019
CVE Published
via MITRE·09:24 PM
Data Sourced
via MITRE·09:24 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2018-20495?
CVE-2018-20495 is classified as a moderate severity vulnerability due to its potential for information exposure.
2
How do I fix CVE-2018-20495?
To fix CVE-2018-20495, upgrade your GitLab installation to version 11.4.13 or later, or 11.5.6 or later, or 11.6.1 or later.
3
What versions of GitLab are affected by CVE-2018-20495?
CVE-2018-20495 affects GitLab Community and Enterprise Editions prior to versions 11.4.13, 11.5.6, and 11.6.1.
4
What type of vulnerability is CVE-2018-20495?
CVE-2018-20495 is an information exposure vulnerability allowing unauthorized access to sensitive data.
5
Is CVE-2018-20495 specific to GitLab?
Yes, CVE-2018-20495 specifically affects the GitLab software platform.