GitLab Community Edition/Enterprise Edition up to 13.4.6/13.5.4/13.6.1 REST API information disclosure

entryeditHistoryDiffjsonxmlCTI
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.
4.1$0-$5k0.00

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 classified as problematic. Affected is an unknown functionality of the component REST API Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. This is going to have an impact on confidentiality. CVE summarizes:

Information about the starred projects for private user profiles was exposed via the GraphQL API starting from 12.2 via the REST API. This affects GitLab >=12.2 to =13.5 to =13.6 to

The weakness was published 12/11/2020. The advisory is shared for download at gitlab.com. This vulnerability is traded as CVE-2020-26415 since 10/01/2020. The exploitability is told to be easy. It is possible to launch the attack remotely. The successful exploitation needs a authentication. There are neither technical details nor an exploit publicly 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.

Productinfoedit

Type

Vendor

Name

CPE 2.3infoedit

CPE 2.2infoedit

CVSSv3infoedit

VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 4.1

VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2infoedit

AVACAuCIA
🔍🔍🔍🔍🔍🔍
🔍🔍🔍🔍🔍🔍
🔍🔍🔍🔍🔍🔍
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfoedit

Class: Information disclosure
CWE: CWE-200
ATT&CK: Unknown

Local: No
Remote: Yes

Availability: 🔒
Status: Not defined

Price Prediction: 🔍
Current Price Estimation: 🔒

0-Dayunlockunlockunlockunlock
Todayunlockunlockunlockunlock

Threat Intelligenceinfoedit

Threat: 🔍
Adversaries: 🔍
Geopolitics: 🔍
Economy: 🔍
Predictions: 🔍
Remediation: 🔍

Countermeasuresinfoedit

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Community Edition/Enterprise Edition 13.4.7/13.5.5/13.6.2
Patch: gitlab.com

Timelineinfoedit

10/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

Sourcesinfoedit

Vendor: https://gitlab.com/

Advisory: gitlab.com
Status: Confirmed
Confirmation: 🔒

CVE: CVE-2020-26415 (🔒)

Entryinfoedit

Created: 12/11/2020 09:53 AM
Updated: 12/15/2020 09:09 PM
Changes: (1) source_cve_cna
Complete: 🔍

Comments

No comments yet. Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!