CVE-2019-15575: Command Injection
Published Dec 18, 2019
·Updated
A command injection exists in GitLab CE/EE <v12.3.2, <v12.2.6, and <v12.1.12 that allowed an attacker to inject commands via the API through the blobs scope.
Affected Software
6 affected components
GitLab GitLab<12.1.12
GitLab GitLab<12.1.12
GitLab GitLab>=12.2.0<12.2.6
GitLab GitLab>=12.2.0<12.2.6
GitLab GitLab>=12.3.0<12.3.2
GitLab GitLab>=12.3.0<12.3.2
Event History
Dec 18, 2019
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
DescriptionWeakness
Frequently Asked Questions
1
What versions of GitLab are affected by CVE-2019-15575?
GitLab CE/EE versions prior to 12.3.2, 12.2.6, and 12.1.12 are affected by CVE-2019-15575.
2
What is the nature of the vulnerability described in CVE-2019-15575?
CVE-2019-15575 is a command injection vulnerability that allows attackers to inject commands via the API through the blobs scope.
3
How serious is the vulnerability CVE-2019-15575?
CVE-2019-15575 is considered a critical severity vulnerability due to its potential for remote command execution.
4
How can I mitigate the risk associated with CVE-2019-15575?
To mitigate CVE-2019-15575, upgrade GitLab to a version that is not affected, specifically to versions 12.3.2 or later, 12.2.6 or later, or 12.1.12 or later.
5
Are both Community and Enterprise editions of GitLab affected by CVE-2019-15575?
Yes, both the Community and Enterprise editions of GitLab are affected by CVE-2019-15575.