GitLab Community Edition/Enterprise Edition up to 13.3.8/13.4.4/13.5.1 Administration Page cross-site request forgery
|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, which was classified as problematic, was 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 part of the component Administration Page. The manipulation with an unknown input leads to a cross site request forgery vulnerability. CWE is classifying the issue as CWE-352. This is going to have an impact on integrity. An attacker might be able force legitimate users to initiate unwanted actions within the web application. The summary by CVE is:
CSRF in runner administration page in all versions of GitLab CE/EE allows an attacker who's able to target GitLab instance administrators to pause/resume runners. Affected versions are >=13.5.0, =13.4.0,
The weakness was presented 11/18/2020. It is possible to read the advisory at hackerone.com. This vulnerability is uniquely identified as CVE-2020-13350 since 05/21/2020. The exploitability is told to be easy. It is possible to initiate the attack remotely. A authentication is necessary for exploitation. It demands that the victim is doing some kind of user interaction. 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: 3.9
VulDB Meta Temp Score: 3.7
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 4.3
NVD Vector: 🔒
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
NVD Base Score: 🔒
ExploitingClass: Cross site request forgery
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/18/2020 +181 days Advisory disclosed
11/18/2020 +0 days VulDB entry created
12/08/2020 +20 days VulDB last update
CVE: CVE-2020-13350 (🔒)
EntryCreated: 11/18/2020 07:00 AM
Updated: 12/08/2020 12:44 PM
Changes: (19) vulnerability_cvss3_nvd_av vulnerability_cvss3_nvd_ac vulnerability_cvss3_nvd_pr vulnerability_cvss3_nvd_ui vulnerability_cvss3_nvd_s vulnerability_cvss3_nvd_c vulnerability_cvss3_nvd_i vulnerability_cvss3_nvd_a 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_cvss3_meta_basescore vulnerability_cvss3_meta_tempscore vulnerability_cvss2_nvd_basescore vulnerability_cvss3_nvd_basescore
Do you want to use VulDB in your project?
Use the official API to access entries easily!