GitLab Community Edition/Enterprise Edition up to 13.3.8/13.4.4/13.5.1 Project Maintainer state issue
|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 classified as problematic has been found in GitLab Community Edition and Enterprise Edition up to 13.3.8/13.4.4/13.5.1 (Bug Tracking Software). This affects an unknown function of the component Project Maintainer Handler. The manipulation with an unknown input leads to a privilege escalation vulnerability. CWE is classifying the issue as CWE-371. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
The Terraform API in GitLab CE/EE 12.10+ exposed the object storage signed URL on the delete operation allowing a malicious project maintainer to overwrite the Terraform state, bypassing audit and other business controls. Affected versions are >=12.10, =13.4, =13.5,
The weakness was presented 11/19/2020. It is possible to read the advisory at gitlab.com. This vulnerability is uniquely identified as CVE-2020-13359 since 05/21/2020. The exploitability is told to be easy. It is possible to initiate the attack remotely. Additional levels of successful authentication are necessary for exploitation. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 13.3.9, 13.4.5 or 13.5.2 eliminates this vulnerability.
CVSSv3VulDB Meta Base Score: 4.7
VulDB Meta Temp Score: 4.5
VulDB Base Score: 4.7
VulDB Temp Score: 4.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
NVD Base Score: 🔒
ExploitingClass: Privilege escalation
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceThreat: 🔍
0-Day Time: 🔒
Upgrade: Community Edition/Enterprise Edition 13.3.9/13.4.5/13.5.2
Timeline05/21/2020 CVE assigned
11/19/2020 +182 days Advisory disclosed
11/19/2020 +0 days VulDB entry created
12/08/2020 +19 days VulDB last update
CVE: CVE-2020-13359 (🔒)
EntryCreated: 11/19/2020 06:45 AM
Updated: 12/08/2020 09:29 PM
Changes: (8) vulnerability_cvss2_nvd_av vulnerability_cvss2_nvd_ac vulnerability_cvss2_nvd_au vulnerability_cvss2_nvd_ci vulnerability_cvss2_nvd_ii vulnerability_cvss2_nvd_ai source_cve_cna vulnerability_cvss2_nvd_basescore
Are you interested in using VulDB?
Download the whitepaper to learn more about our service!