GitLab Enterprise Edition up to 13.6.1 Group Member 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 has been found in GitLab Enterprise Edition up to 13.6.1 (Bug Tracking Software) and classified as problematic. This vulnerability affects some unknown processing of the component Group Member Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. As an impact it is known to affect confidentiality. CVE summarizes:
Removed group members were able to use the To-Do functionality to retrieve updated information on confidential epics starting in GitLab EE 13.2 before 13.6.2.
The weakness was presented 12/11/2020. The advisory is available at gitlab.com. This vulnerability was named CVE-2020-26412 since 10/01/2020. The exploitation appears to be difficult. The attack can be initiated remotely. Required for exploitation is a single authentication. The technical details are unknown and an exploit is not available.
Upgrading to version 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: 3.1
VulDB Meta Temp Score: 3.0
VulDB Base Score: 3.1
VulDB Temp Score: 3.0
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: Enterprise Edition 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-26412 (🔒)
EntryCreated: 12/11/2020 09:51 AM
Updated: 12/15/2020 08:49 PM
Changes: (1) source_cve_cna
Interested in the pricing of exploits?
See the underground prices here!