First published: Tue Mar 28 2017(Updated: )
Multiple versions of GitLab expose a dangerous method to any authenticated user that could lead to the deletion of all Issue and MergeRequest objects on a GitLab instance. For GitLab instances with publicly available projects this vulnerability could be exploited by an unauthenticated user. A fix was included in versions 8.14.3, 8.13.8, and 8.12.11, which were released on December 5th 2016 at 3:59 PST. The GitLab versions vulnerable to this are 8.13.0, 8.13.0-ee, 8.13.1, 8.13.1-ee, 8.13.2, 8.13.2-ee, 8.13.3, 8.13.3-ee, 8.13.4, 8.13.4-ee, 8.13.5, 8.13.5-ee, 8.13.6, 8.13.6-ee, 8.13.7, 8.14.0, 8.14.0-ee, 8.14.1, 8.14.2, and 8.14.2-ee.
Credit: support@hackerone.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | =8.13.0 | |
GitLab | =8.13.0 | |
GitLab | =8.13.1 | |
GitLab | =8.13.1 | |
GitLab | =8.13.2 | |
GitLab | =8.13.2 | |
GitLab | =8.13.3 | |
GitLab | =8.13.3 | |
GitLab | =8.13.4 | |
GitLab | =8.13.4 | |
GitLab | =8.13.5 | |
GitLab | =8.13.5 | |
GitLab | =8.13.6 | |
GitLab | =8.13.6 | |
GitLab | =8.13.7 | |
GitLab | =8.13.7 | |
GitLab | =8.14.0 | |
GitLab | =8.14.0 | |
GitLab | =8.14.1 | |
GitLab | =8.14.1 | |
GitLab | =8.14.2 | |
GitLab | =8.14.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-9469 has a high severity rating due to its potential to allow authenticated users to delete critical Issue and MergeRequest objects on GitLab.
To fix CVE-2016-9469, GitLab administrators should upgrade to a patched version of GitLab that addresses this vulnerability.
CVE-2016-9469 affects GitLab versions 8.13.0 through 8.14.2 inclusive.
Yes, CVE-2016-9469 can be exploited by unauthenticated users on GitLab instances with publicly available projects.
User authentication is not required to exploit CVE-2016-9469 when the GitLab projects are publicly accessible.