CVE-2017-0916: Input Validation
Published Mar 21, 2018
·Updated
Gitlab Community Edition version 10.3 is vulnerable to a lack of input validation in the systemhookpush queue through web hook component resulting in remote code execution.
Affected Software
8 affected componentsFixes available
debian/gitlab
16.0.8+ds1-2
GitLab GitLab>=8.8.0<=10.1.5
GitLab GitLab>=8.8.0<=10.1.5
GitLab GitLab>=10.2.0<=10.2.5
GitLab GitLab>=10.2.0<=10.2.5
GitLab GitLab>=10.3.0<=10.3.3
GitLab GitLab>=10.3.0<=10.3.3
Debian Debian Linux=9.0
Event History
Mar 21, 2018
CVE Published
via MITRE·08:00 PM
Data Sourced
via MITRE·08:00 PM
DescriptionWeakness
Frequently Asked Questions
1
What is the severity of CVE-2017-0916?
CVE-2017-0916 is classified as a critical vulnerability due to the potential for remote code execution.
2
How do I fix CVE-2017-0916?
To mitigate CVE-2017-0916, upgrade GitLab to version 10.3.4 or later, or apply any available patches.
3
Which versions of GitLab are affected by CVE-2017-0916?
CVE-2017-0916 affects GitLab Community and Enterprise Editions from version 8.8.0 to 10.3.3.
4
What is the nature of the vulnerability in CVE-2017-0916?
CVE-2017-0916 involves a lack of input validation in the system_hook_push queue through the web hook component.
5
Is CVE-2017-0916 associated with GitLab's web hook functionality?
Yes, CVE-2017-0916 specifically impacts the web hook functionality within GitLab.