GitLab Runner up to 14.3.4/14.4.2/14.5.2 Trace File file descriptor consumption

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

Summaryinfo

A vulnerability identified as problematic has been detected in GitLab Runner up to 14.3.4/14.4.2/14.5.2. This issue affects some unknown processing of the component Trace File Handler. Performing a manipulation results in file descriptor consumption. This vulnerability is known as CVE-2021-39947. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in GitLab Runner up to 14.3.4/14.4.2/14.5.2 (Bug Tracking Software). This affects some unknown functionality of the component Trace File Handler. The manipulation with an unknown input leads to a file descriptor consumption vulnerability. CWE is classifying the issue as CWE-769. This entry has been deprecated because it was a duplicate of CWE-774. All content has been transferred to CWE-774. This is going to have an impact on confidentiality.

The weakness was published 06/06/2022 as 28732. It is possible to read the advisory at gitlab.com. This vulnerability is uniquely identified as CVE-2021-39947 since 08/23/2021. The technical details are unknown and an exploit is not publicly available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.2
VulDB Meta Temp Score: 4.2

VulDB Base Score: 3.1
VulDB Temp Score: 3.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 5.3
CNA Vector (GitLab Inc.): 🔍

CVSSv2info

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

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

Exploitinginfo

Class: File descriptor consumption
CWE: CWE-769 / CWE-400 / CWE-404
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: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

08/23/2021 🔍
06/06/2022 +287 days 🔍
06/06/2022 +0 days 🔍
06/08/2022 +2 days 🔍

Sourcesinfo

Vendor: gitlab.com

Advisory: 28732
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2021-39947 (🔍)
GCVE (CVE): GCVE-0-2021-39947
GCVE (VulDB): GCVE-100-201315

Entryinfo

Created: 06/06/2022 21:10
Updated: 06/08/2022 12:39
Changes: 06/06/2022 21:10 (40), 06/08/2022 12:32 (1), 06/08/2022 12:39 (12)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!