GitLab Community Edition/Enterprise Edition up to 18.0.5/18.1.3/18.2.1 allocation of resources
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in GitLab Community Edition and Enterprise Edition up to 18.0.5/18.1.3/18.2.1. The impacted element is an unknown function. The manipulation leads to allocation of resources. This vulnerability is uniquely identified as CVE-2025-2614. The attack is possible to be carried out remotely. No exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in GitLab Community Edition and Enterprise Edition up to 18.0.5/18.1.3/18.2.1. This issue affects some unknown processing. The manipulation with an unknown input leads to a allocation of resources vulnerability. Using CWE to declare the problem leads to 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. Impacted is availability. The summary by CVE is:
An issue has been discovered in GitLab CE/EE affecting all versions from 11.6 before 18.0.6, 18.1 before 18.1.4, and 18.2 before 18.2.2 that could have allowed an authenticated user to cause a denial of service condition by creating specially crafted content that consumes excessive server resources when processed.
The weakness was disclosed by pwnie as 526349. The advisory is shared at gitlab.com. The identification of this vulnerability is CVE-2025-2614 since 03/21/2025. The exploitation is known to be easy. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
Upgrading to version 18.0.6, 18.1.4 or 18.2.2 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2025-1816). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Open Source GitLab
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: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
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 18.0.6/18.1.4/18.2.2
Timeline
03/21/2025 CVE reserved08/13/2025 Advisory disclosed
08/13/2025 VulDB entry created
08/14/2025 VulDB entry last update
Sources
Vendor: gitlab.comAdvisory: 526349
Researcher: pwnie
Status: Confirmed
CVE: CVE-2025-2614 (🔒)
GCVE (CVE): GCVE-0-2025-2614
GCVE (VulDB): GCVE-100-319997
CERT Bund: WID-SEC-2025-1816 - GitLab: Mehrere Schwachstellen
Entry
Created: 08/13/2025 20:38Updated: 08/14/2025 16:51
Changes: 08/13/2025 20:38 (65), 08/13/2025 21:25 (7), 08/14/2025 16:51 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.