GitLab Community Edition/Enterprise Edition up to 17.2.8/17.3.4/17.4.1 algorithmic complexity
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in GitLab Community Edition and Enterprise Edition up to 17.2.8/17.3.4/17.4.1. Affected by this issue is some unknown functionality. Executing a manipulation can lead to algorithmic complexity. The identification of this vulnerability is CVE-2024-9631. The attack may be launched remotely. There is no exploit available. The affected component should be upgraded.
Details
A vulnerability classified as problematic was found in GitLab Community Edition and Enterprise Edition up to 17.2.8/17.3.4/17.4.1. This vulnerability affects an unknown part. The manipulation with an unknown input leads to a algorithmic complexity vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect availability. CVE summarizes:
An issue was discovered in GitLab CE/EE affecting all versions starting from 13.6 prior to 17.2.9, starting from 17.3 prior to 17.3.5, and starting from 17.4 prior to 17.4.2, where viewing diffs of MR with conflicts can be slow.
The weakness was shared by a92847865 as 480867. The advisory is shared for download at gitlab.com. This vulnerability was named CVE-2024-9631 since 10/08/2024. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1499.
Upgrading to version 17.2.9, 17.3.5 or 17.4.2 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://gitlab.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA Vector (GitLab): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Algorithmic complexityCWE: 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-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Community Edition/Enterprise Edition 17.2.9/17.3.5/17.4.2
Timeline
10/08/2024 🔍02/05/2025 🔍
02/05/2025 🔍
08/06/2025 🔍
Sources
Vendor: gitlab.comAdvisory: 480867
Researcher: a92847865
Status: Confirmed
CVE: CVE-2024-9631 (🔍)
GCVE (CVE): GCVE-0-2024-9631
GCVE (VulDB): GCVE-100-294724
Entry
Created: 02/05/2025 12:28Updated: 08/06/2025 21:43
Changes: 02/05/2025 12:28 (66), 08/06/2025 21:43 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.