CVE-2018-20488: Infoleak

Published Dec 30, 2019
·
Updated

An issue was discovered in GitLab Community and Enterprise Edition 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>=9.3.0<11.4.13
GitLab GitLab>=9.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-20488?

CVE-2018-20488 has been classified as a high severity vulnerability due to the potential for information exposure.

2

How do I fix CVE-2018-20488?

To fix CVE-2018-20488, upgrade GitLab Community or Enterprise Edition to versions 11.4.13, 11.5.6, or 11.6.1 or later.

3

What versions are affected by CVE-2018-20488?

CVE-2018-20488 affects GitLab Community and Enterprise Edition versions prior to 11.4.13, 11.5.x prior to 11.5.6, and 11.6.x prior to 11.6.1.

4

What type of vulnerability is CVE-2018-20488?

CVE-2018-20488 is categorized as an Information Exposure vulnerability.

5

Can I still use my GitLab if it is affected by CVE-2018-20488?

While you can continue to use your GitLab instance, it is highly recommended to apply the fix to mitigate the risks associated with CVE-2018-20488.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203