GitLab Community Edition/Enterprise Edition up to 13.4.6/13.5.4/13.6.1 Project information disclosure
|CVSS Meta Temp Score|
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
|Current Exploit Price (≈)|
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
|CTI Interest Score|
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
A vulnerability was found in GitLab Community Edition and Enterprise Edition up to 13.4.6/13.5.4/13.6.1 (Bug Tracking Software). It has been rated as problematic. Affected by this issue is an unknown part of the component Project Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. Impacted is confidentiality. CVE summarizes:
Information disclosure via GraphQL in GitLab CE/EE 13.1 and later exposes private group and project membership. This affects versions >=13.6 to =13.5 to =13.1 to
The weakness was disclosed 12/11/2020. The advisory is available at gitlab.com. This vulnerability is handled as CVE-2020-26417 since 10/01/2020. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. The technical details are unknown and an exploit is not available.
Upgrading to version 13.4.7, 13.5.5 or 13.6.2 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at gitlab.com. The best possible mitigation is suggested to be upgrading to the latest version.
CVSSv3VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
ExploitingClass: Information disclosure
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceThreat: 🔍
0-Day Time: 🔒
Upgrade: Community Edition/Enterprise Edition 13.4.7/13.5.5/13.6.2
Timeline10/01/2020 CVE assigned
12/11/2020 +71 days Advisory disclosed
12/11/2020 +0 days VulDB entry created
12/15/2020 +4 days VulDB last update
CVE: CVE-2020-26417 (🔒)
EntryCreated: 12/11/2020 09:57 AM
Updated: 12/15/2020 09:26 PM
Changes: (1) source_cve_cna
Want to stay up to date on a daily basis?
Enable the mail alert feature now!