First published: Wed Mar 21 2018(Updated: )
Gitlab Community and Enterprise Editions version 10.3.3 is vulnerable to an Insecure Temporary File in the project import component resulting remote code execution.
Credit: support@hackerone.com
Affected Software | Affected Version | How to fix |
---|---|---|
debian/gitlab | 16.0.8+ds1-2 | |
GitLab | >=8.9.0<=9.5.10 | |
GitLab | >=8.9.0<=9.5.10 | |
GitLab | >=10.0.0<=10.1.5 | |
GitLab | >=10.0.0<=10.1.15 | |
GitLab | >10.2.0<=10.2.5 | |
GitLab | >=10.2.0<=10.2.5 | |
GitLab | >10.3.0<=10.3.3 | |
GitLab | >=10.3.0<=10.3.3 | |
Debian Debian Linux | =9.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2018-3710 has a high severity rating due to its potential to allow remote code execution.
To fix CVE-2018-3710, upgrade GitLab to version 10.3.4 or later.
CVE-2018-3710 affects GitLab Community and Enterprise Editions from version 8.9.0 to 10.3.3.
The impact of CVE-2018-3710 includes the risk of remote code execution due to insecure temporary file handling.
Yes, CVE-2018-3710 is present in GitLab packages on Debian systems prior to the patched version.