GitLab Community Edition/Enterprise Edition up to 10.1.5/10.2.5/10.3.3 Import missing authentication

Summaryinfo

A vulnerability categorized as critical has been discovered in GitLab Community Edition and Enterprise Edition up to 10.1.5/10.2.5/10.3.3. This issue affects some unknown processing of the component Import. Such manipulation leads to missing authentication. This vulnerability is uniquely identified as CVE-2017-0919. The attack can be launched remotely. No exploit exists. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in GitLab Community Edition and Enterprise Edition up to 10.1.5/10.2.5/10.3.3 (Bug Tracking Software). It has been rated as critical. Affected by this issue is an unknown functionality of the component Import. The manipulation with an unknown input leads to a missing authentication vulnerability. Using CWE to declare the problem leads to CWE-306. The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. Impacted is confidentiality, integrity, and availability. CVE summarizes:

GitLab Community and Enterprise Editions before 10.1.6, 10.2.6, and 10.3.4 are vulnerable to an authorization bypass issue in the GitLab import component resulting in an attacker being able to perform operations under a group in which they were previously unauthorized.

The bug was discovered 05/25/2018. The weakness was disclosed 07/03/2018 (Website). The advisory is shared for download at hackerone.com. This vulnerability is handled as CVE-2017-0919 since 11/30/2016. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available.

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

Upgrading to version 10.1.6, 10.2.6 or 10.3.4 eliminates this vulnerability.

The entry VDB-120213 is pretty similar. Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• Bug Tracking Software

Vendor

• GitLab

Name

• Community Edition
• Enterprise Edition

Version

• 10.1.0
• 10.1.1
• 10.1.2
• 10.1.3
• 10.1.4
• 10.1.5
• 10.2.0
• 10.2.1
• 10.2.2
• 10.2.3
• 10.2.4
• 10.2.5
• 10.3.0
• 10.3.1
• 10.3.2
• 10.3.3

License

• open-source

Website

• Vendor: https://gitlab.com/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion