What is the severity of CVE-2018-18640?

CVE-2018-18640 has a medium severity rating due to the potential for information exposure.

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.

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.

What type of vulnerability is CVE-2018-18640?

CVE-2018-18640 is classified as an information exposure vulnerability through browser caching.

Is CVE-2018-18640 related to data privacy?

Yes, CVE-2018-18640 potentially compromises data privacy by exposing sensitive information through browser caches.

Vulnerability/
CVE-2018-18640

medium

6.5

CWE

200

4/12/2018

5/8/2024

CVE-2018-18640: Infoleak

First published: Tue Dec 04 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.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	<11.2.7
GitLab	<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-18640?
CVE-2018-18640 has a medium severity rating due to the potential for information exposure.
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.
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.
What type of vulnerability is CVE-2018-18640?
CVE-2018-18640 is classified as an information exposure vulnerability through browser caching.
Is CVE-2018-18640 related to data privacy?
Yes, CVE-2018-18640 potentially compromises data privacy by exposing sensitive information through browser caches.

agent/type
agent/references
agent/severity
agent/weakness
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/event
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
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-18640?
CVE-2018-18640 has a medium severity rating due to the potential for information exposure.
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.
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.
What type of vulnerability is CVE-2018-18640?
CVE-2018-18640 is classified as an information exposure vulnerability through browser caching.
Is CVE-2018-18640 related to data privacy?
Yes, CVE-2018-18640 potentially compromises data privacy by exposing sensitive information through browser caches.