GitLab Community Edition/Enterprise Edition 10.1/10.2/10.2.4 MilestoneFinder sql injection

Summaryinfo

A vulnerability was found in GitLab Community Edition and Enterprise Edition 10.1/10.2/10.2.4. It has been rated as critical. This impacts an unknown function of the component MilestoneFinder. Performing a manipulation results in sql injection. This vulnerability is cataloged as CVE-2017-0914. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability classified as critical has been found in GitLab Community Edition and Enterprise Edition 10.1/10.2/10.2.4 (Bug Tracking Software). This affects an unknown function of the component MilestoneFinder. The manipulation with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Gitlab Community and Enterprise Editions version 10.1, 10.2, and 10.2.4 are vulnerable to a SQL injection in the MilestoneFinder component resulting in disclosure of all data in a GitLab instance's database.

The bug was discovered 01/16/2018. The weakness was shared 03/21/2018 (Website). The advisory is shared at about.gitlab.com. This vulnerability is uniquely identified as CVE-2017-0914 since 11/30/2016. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1505 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 64 days. During that time the estimated underground price was around $0-$5k.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The entries VDB-114850, VDB-114851, VDB-114852 and VDB-114853 are related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Bug Tracking Software

Vendor

• GitLab

Name

• Community Edition
• Enterprise Edition

Version

• 10.1
• 10.2
• 10.2.4

License

• open-source

Website

• Vendor: https://gitlab.com/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion