GitLab Community Edition/Enterprise Edition up to 17.4.4/17.5.2/17.6.0 Harbor Registry algorithmic complexity

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

Summaryinfo

A vulnerability identified as problematic has been detected in GitLab Community Edition and Enterprise Edition up to 17.4.4/17.5.2/17.6.0. This affects an unknown part of the component Harbor Registry Handler. The manipulation leads to algorithmic complexity. This vulnerability is documented as CVE-2024-8177. The attack can be initiated remotely. There is not any exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in GitLab Community Edition and Enterprise Edition up to 17.4.4/17.5.2/17.6.0. This issue affects some unknown functionality of the component Harbor Registry Handler. The manipulation with an unknown input leads to a algorithmic complexity vulnerability. Using CWE to declare the problem leads to CWE-407. An algorithm in a product has an inefficient worst-case computational complexity that may be detrimental to system performance and can be triggered by an attacker, typically using crafted manipulations that ensure that the worst case is being reached. Impacted is availability. The summary by CVE is:

An issue was discovered in GitLab CE/EE affecting all versions starting from 15.6 prior to 17.4.5, starting from 17.5 prior to 17.5.3, starting from 17.6 prior to 17.6.1 which could cause Denial of Service via integrating a malicious harbor registry.

The weakness was released by a92847865 as 480706. It is possible to read the advisory at gitlab.com. The identification of this vulnerability is CVE-2024-8177 since 08/26/2024. The exploitation is known to be difficult. The attack may be initiated remotely. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.

The vulnerability scanner Nessus provides a plugin with the ID 211859 (GitLab 15.6 < 17.4.5 / 17.5 < 17.5.3 / 17.6 < 17.6.1 (CVE-2024-8177)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 17.4.5, 17.5.3 or 17.6.1 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (211859). 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.1

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

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

CVSSv2info

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

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

Exploitinginfo

Class: Algorithmic complexity
CWE: CWE-407 / 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

Nessus ID: 211859
Nessus Name: GitLab 15.6 < 17.4.5 / 17.5 < 17.5.3 / 17.6 < 17.6.1 (CVE-2024-8177)

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Community Edition/Enterprise Edition 17.4.5/17.5.3/17.6.1

Timelineinfo

08/26/2024 🔍
11/26/2024 +92 days 🔍
11/27/2024 +0 days 🔍
11/27/2024 +0 days 🔍

Sourcesinfo

Vendor: gitlab.com

Advisory: 480706
Researcher: a92847865
Status: Confirmed

CVE: CVE-2024-8177 (🔍)
GCVE (CVE): GCVE-0-2024-8177
GCVE (VulDB): GCVE-100-286211

Entryinfo

Created: 11/27/2024 00:18
Updated: 11/27/2024 03:13
Changes: 11/27/2024 00:18 (67), 11/27/2024 03:13 (2)
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 ▸

Want to know what is going to be exploited?

We predict KEV entries!