GitLab Community Edition/Enterprise Edition up to 17.9.7/17.10.5/17.11.1 GitHub Import Request allocation of resources
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in GitLab Community Edition and Enterprise Edition up to 17.9.7/17.10.5/17.11.1 and classified as critical. Affected by this vulnerability is an unknown functionality of the component GitHub Import Request Handler. Executing a manipulation can lead to allocation of resources. This vulnerability is tracked as CVE-2024-8973. The attack can be launched remotely. No exploit exists. It is suggested to upgrade the affected component.
Details
A vulnerability classified as critical was found in GitLab Community Edition and Enterprise Edition up to 17.9.7/17.10.5/17.11.1. This vulnerability affects an unknown code of the component GitHub Import Request 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. CVE summarizes:
An issue has been discovered in GitLab CE/EE affecting all versions starting from 17.1 prior to 17.9.8, from 17.10 prior to 17.10.6, and from 17.11 prior to 17.11.2. It was possible to cause a DoS condition via GitHub import requests using a malicious crafted payload.
The weakness was disclosed by a92847865 as 491041. The advisory is available at gitlab.com. This vulnerability was named CVE-2024-8973 since 09/18/2024. The exploitation appears to be easy. The attack can be initiated remotely. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1499 by the MITRE ATT&CK project.
Upgrading to version 17.9.8, 17.10.6 or 17.11.2 eliminates this vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
- 17.9.0
- 17.9.1
- 17.9.2
- 17.9.3
- 17.9.4
- 17.9.5
- 17.9.6
- 17.9.7
- 17.10.0
- 17.10.1
- 17.10.2
- 17.10.3
- 17.10.4
- 17.10.5
- 17.11.0
- 17.11.1
License
Website
- Vendor: https://gitlab.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.7
VulDB Base Score: 6.5
VulDB Temp Score: 6.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CNA Base Score: 6.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: Allocation of resourcesCWE: CWE-770 / 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-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.9.8/17.10.6/17.11.2
Timeline
09/18/2024 🔍05/09/2025 🔍
05/09/2025 🔍
08/08/2025 🔍
Sources
Vendor: gitlab.comAdvisory: 491041
Researcher: a92847865
Status: Confirmed
CVE: CVE-2024-8973 (🔍)
GCVE (CVE): GCVE-0-2024-8973
GCVE (VulDB): GCVE-100-308242
Entry
Created: 05/09/2025 23:56Updated: 08/08/2025 19:10
Changes: 05/09/2025 23:56 (67), 08/08/2025 19:10 (12)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.