CVE-2018-18640: Infoleak
Published Dec 4, 2018
·Updated
An issue was discovered in GitLab Community and Enterprise Edition before 11.2.7, 11.3.x before 11.3.8, and 11.4.x before 11.4.3. It has Information Exposure Through Browser Caching.
Affected Software
6 affected components
GitLab GitLab<11.2.7
GitLab GitLab<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-18640?
CVE-2018-18640 has a medium severity rating due to the potential for information exposure.
2
How do I fix CVE-2018-18640?
To fix CVE-2018-18640, upgrade GitLab to version 11.2.7 or later, or to versions 11.3.8 or 11.4.3 or later.
3
What software versions are affected by CVE-2018-18640?
CVE-2018-18640 affects GitLab Community and Enterprise Editions prior to versions 11.2.7, 11.3.8, and 11.4.3.
4
What type of vulnerability is CVE-2018-18640?
CVE-2018-18640 is classified as an information exposure vulnerability through browser caching.
5
Is CVE-2018-18640 related to data privacy?
Yes, CVE-2018-18640 potentially compromises data privacy by exposing sensitive information through browser caches.