GitLab Community/Enterprise up to 11.6.9/11.7.5/11.8.0 Access Control access control

Summaryinfo

A vulnerability identified as critical has been detected in GitLab Community and Enterprise up to 11.6.9/11.7.5/11.8.0. Impacted is an unknown function of the component Access Control. The manipulation leads to access control. This vulnerability is uniquely identified as CVE-2019-9170. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in GitLab Community and Enterprise up to 11.6.9/11.7.5/11.8.0 (Bug Tracking Software) and classified as critical. This issue affects some unknown functionality of the component Access Control. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

An issue was discovered in GitLab Community and Enterprise Edition before 11.6.10, 11.7.x before 11.7.6, and 11.8.x before 11.8.1. It has Incorrect Access Control.

The bug was discovered 03/04/2019. The weakness was disclosed 04/17/2019 (Website). The advisory is shared at about.gitlab.com. The identification of this vulnerability is CVE-2019-9170 since 02/26/2019. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 44 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 255091 (Linux Distros Unpatched Vulnerability : CVE-2019-9170), which helps to determine the existence of the flaw in a target environment. The commercial vulnerability scanner Qualys is able to test this issue with plugin 371751 (GitLab Multiple Security Vulnerability).

Upgrading to version 11.6.10, 11.7.6 or 11.8.1 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (255091). The entries VDB-133458, VDB-133459, VDB-133460 and VDB-133461 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Bug Tracking Software

Vendor

• GitLab

Name

• Community
• Enterprise

Version

• 11.0
• 11.1
• 11.2
• 11.3
• 11.4
• 11.5
• 11.6
• 11.6.0
• 11.6.1
• 11.6.2
• 11.6.3
• 11.6.4
• 11.6.5
• 11.6.6
• 11.6.7
• 11.6.8
• 11.6.9
• 11.7
• 11.7.0
• 11.7.1
• 11.7.2
• 11.7.3
• 11.7.4
• 11.7.5
• 11.8.0

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