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.
The product provides an Applications Programming Interface (API) or similar interface for interaction with external actors, but the interface includes a dangerous method or function that is not properly restricted.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Gitlab | Gitlab | 8.13.0 (including) | 8.13.0 (including) |
| Gitlab | Gitlab | 8.13.1 (including) | 8.13.1 (including) |
| Gitlab | Gitlab | 8.13.2 (including) | 8.13.2 (including) |
| Gitlab | Gitlab | 8.13.3 (including) | 8.13.3 (including) |
| Gitlab | Gitlab | 8.13.4 (including) | 8.13.4 (including) |
| Gitlab | Gitlab | 8.13.5 (including) | 8.13.5 (including) |
| Gitlab | Gitlab | 8.13.6 (including) | 8.13.6 (including) |
| Gitlab | Gitlab | 8.13.7 (including) | 8.13.7 (including) |
| Gitlab | Gitlab | 8.14.0 (including) | 8.14.0 (including) |
| Gitlab | Gitlab | 8.14.1 (including) | 8.14.1 (including) |
| Gitlab | Gitlab | 8.14.2 (including) | 8.14.2 (including) |
| Gitlab | Ubuntu | artful | * |
| Gitlab | Ubuntu | zesty | * |
This weakness can lead to a wide variety of resultant weaknesses, depending on the behavior of the exposed method. It can apply to any number of technologies and approaches, such as ActiveX controls, Java functions, IOCTLs, and so on. The exposure can occur in a few different ways:
Identify all exposed functionality. Explicitly list all functionality that must be exposed to some user or set of users. Identify which functionality may be:
Ensure that the implemented code follows these expectations. This includes setting the appropriate access modifiers where applicable (public, private, protected, etc.) or not marking ActiveX controls safe-for-scripting.