CVE-2019-15733: Infoleak
Published 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.
Affected Software
6 affected components
GitLab GitLab>=7.12.0<12.0.8
GitLab GitLab>=7.12.0<12.0.8
GitLab GitLab>=12.1.0<12.1.8
GitLab GitLab>=12.1.0<12.1.8
GitLab GitLab>=12.2.0<12.2.3
GitLab GitLab>=12.2.0<12.2.3
Event History
Sep 16, 2019
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
Description
Frequently Asked Questions
1
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.
2
How do I fix CVE-2019-15733?
To mitigate CVE-2019-15733, update GitLab to version 12.2.3 or later.
3
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.
4
Does CVE-2019-15733 affect both Community and Enterprise editions of GitLab?
Yes, CVE-2019-15733 affects both GitLab Community Edition and Enterprise Edition.
5
What does CVE-2019-15733 expose to unauthorized users?
CVE-2019-15733 exposes the specified default branch name to unauthorized users.