CWE
200
Advisory Published
Updated

CVE-2019-15733: Infoleak

First published: Mon Sep 16 2019(Updated: )

An issue was discovered in GitLab Community and Enterprise Edition 7.12 through 12.2.1. The specified default branch name could be exposed to unauthorized users.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
GitLab>=7.12.0<12.0.8
GitLab>=7.12.0<12.0.8
GitLab>=12.1.0<12.1.8
GitLab>=12.1.0<12.1.8
GitLab>=12.2.0<12.2.3
GitLab>=12.2.0<12.2.3

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2019-15733?

    CVE-2019-15733 is considered a medium severity vulnerability due to its potential to expose sensitive repository information.

  • How do I fix CVE-2019-15733?

    To mitigate CVE-2019-15733, update GitLab to version 12.2.3 or later.

  • Which GitLab versions are affected by CVE-2019-15733?

    CVE-2019-15733 affects GitLab Community and Enterprise Editions from versions 7.12 to 12.2.1.

  • Does CVE-2019-15733 affect both Community and Enterprise editions of GitLab?

    Yes, CVE-2019-15733 affects both GitLab Community Edition and Enterprise Edition.

  • What does CVE-2019-15733 expose to unauthorized users?

    CVE-2019-15733 exposes the specified default branch name to unauthorized users.

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