CVE-2019-15575: Command Injection
First published: Wed 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.
Credit: support@hackerone.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | <12.1.12 | |
| GitLab | <12.1.12 | |
| GitLab | >=12.2.0<12.2.6 | |
| GitLab | >=12.2.0<12.2.6 | |
| GitLab | >=12.3.0<12.3.2 | |
| GitLab | >=12.3.0<12.3.2 |
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.
Reference Links
Frequently Asked Questions
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.
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.
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.
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.
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.
- agent/type
- agent/references
- agent/severity
- agent/weakness
- agent/author
- agent/softwarecombine
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/gitlab
- canonical/gitlab
- version/gitlab/12.2.0
- version/gitlab/12.3.0