GitLab Enterprise Edition up to 17.7.6/17.8.4/17.9.1 allocation of resources

Summaryinfo

A vulnerability identified as problematic has been detected in GitLab Enterprise Edition up to 17.7.6/17.8.4/17.9.1. This affects an unknown part. The manipulation leads to allocation of resources. This vulnerability is traded as CVE-2025-1257. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in GitLab Enterprise Edition up to 17.7.6/17.8.4/17.9.1. It has been rated as problematic. This issue affects some unknown functionality. 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 was discovered in GitLab EE affecting all versions starting with 12.3 before 17.7.7, 17.8 prior to 17.8.5, and 17.9 prior to 17.9.2. A vulnerability in certain GitLab instances could allow an attacker to cause a denial of service condition by manipulating specific API inputs.

The weakness was shared by pwnie. The advisory is shared at gitlab.com. The identification of this vulnerability is CVE-2025-1257 since 02/12/2025. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.

The vulnerability scanner Nessus provides a plugin with the ID 232673 (GitLab 12.3 < 17.7.7 / 17.8 < 17.8.5 / 17.9 < 17.9.2 (CVE-2025-1257)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 17.7.7, 17.8.5 or 17.9.2 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (232673). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Bug Tracking Software

Vendor

• GitLab

Name

• Enterprise Edition

Version

• 17.7.0
• 17.7.1
• 17.7.2
• 17.7.3
• 17.7.4
• 17.7.5
• 17.7.6
• 17.8.0
• 17.8.1
• 17.8.2
• 17.8.3
• 17.8.4
• 17.9.0
• 17.9.1

License

• commercial

Website

• Vendor: https://gitlab.com/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion