GitLab Runner up to 13.2.9/13.3.6/13.4.1 Runner Configuration privilege escalation

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

Summaryinfo

A vulnerability, which was classified as problematic, has been found in GitLab Runner up to 13.2.9/13.3.6/13.4.1. Affected by this vulnerability is an unknown functionality of the component Runner Configuration Handler. The manipulation leads to an unknown weakness. This vulnerability is listed as CVE-2020-13327. There is no available exploit. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in GitLab Runner up to 13.2.9/13.3.6/13.4.1 (Bug Tracking Software). It has been rated as problematic. This issue affects an unknown functionality of the component Runner Configuration Handler. The impact remains unknown.

The weakness was presented 10/23/2020. The advisory is shared at gitlab.com. The identification of this vulnerability is CVE-2020-13327. Neither technical details nor an exploit are publicly available.

Upgrading to version 13.2.10, 13.3.7 or 13.4.2 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 6.4

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

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

NVD Base Score: 🔍

Exploitinginfo

Class: Privilege escalation
CWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: GitLab Runner 13.2.10/13.3.7/13.4.2

Timelineinfo

05/21/2020 🔍
10/23/2020 +155 days 🔍
10/23/2020 +0 days 🔍
11/26/2020 +34 days 🔍

Sourcesinfo

Advisory: gitlab.com
Status: Not defined
Confirmation: 🔍

CVE: CVE-2020-13327 (🔍)
GCVE (CVE): GCVE-0-2020-13327
GCVE (VulDB): GCVE-100-163493

Entryinfo

Created: 10/23/2020 12:14
Updated: 11/26/2020 14:03
Changes: 10/23/2020 12:14 (36), 11/26/2020 13:58 (3), 11/26/2020 14:03 (19)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!