GitLab Community Edition/Enterprise Edition up to 17.8.5/17.9.2/17.10.0 File allocation of resources
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in GitLab Community Edition and Enterprise Edition up to 17.8.5/17.9.2/17.10.0. Impacted is an unknown function of the component File Handler. This manipulation causes allocation of resources. This vulnerability is tracked as CVE-2024-10307. The attack is possible to be carried out remotely. No exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability was found in GitLab Community Edition and Enterprise Edition up to 17.8.5/17.9.2/17.10.0. It has been declared as problematic. Affected by this vulnerability is some unknown processing of the component File Handler. The manipulation with an unknown input leads to a allocation of resources vulnerability. The CWE definition for the vulnerability is CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. As an impact it is known to affect availability. The summary by CVE is:
An issue has been discovered in GitLab EE/CE affecting all versions from 12.10 before 17.8.6, 17.9 before 17.9.3, and 17.10 before 17.10.1. A maliciously crafted file can cause uncontrolled CPU consumption when viewing the associated merge request.
The weakness was disclosed by l33thaxor as 500497. It is possible to read the advisory at gitlab.com. This vulnerability is known as CVE-2024-10307 since 10/23/2024. The exploitation appears to be easy. The attack can be launched 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.
Upgrading to version 17.8.6, 17.9.3 or 17.10.1 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
- 17.0
- 17.1
- 17.2
- 17.3
- 17.4
- 17.5
- 17.6
- 17.7
- 17.8
- 17.8.0
- 17.8.1
- 17.8.2
- 17.8.3
- 17.8.4
- 17.8.5
- 17.9
- 17.9.0
- 17.9.1
- 17.9.2
- 17.10.0
License
Website
- Vendor: https://gitlab.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.7VulDB Meta Temp Score: 4.6
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
CNA Base Score: 4.3
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: Allocation of resourcesCWE: CWE-770 / CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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.8.6/17.9.3/17.10.1
Timeline
10/23/2024 🔍03/28/2025 🔍
03/28/2025 🔍
08/13/2025 🔍
Sources
Vendor: gitlab.comAdvisory: 500497
Researcher: l33thaxor
Status: Confirmed
CVE: CVE-2024-10307 (🔍)
GCVE (CVE): GCVE-0-2024-10307
GCVE (VulDB): GCVE-100-301867
Entry
Created: 03/28/2025 11:47Updated: 08/13/2025 05:08
Changes: 03/28/2025 11:47 (66), 08/13/2025 05:08 (12)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.