GitLab Community Edition/Enterprise Edition up to 17.4.5/17.5.3/17.6.1 GraphQL Query authorization

Summaryinfo

A vulnerability has been found in GitLab Community Edition and Enterprise Edition up to 17.4.5/17.5.3/17.6.1 and classified as problematic. This issue affects some unknown processing of the component GraphQL Query Handler. Performing a manipulation results in authorization. This vulnerability is identified as CVE-2024-8116. The attack can be initiated remotely. There is not any exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in GitLab Community Edition and Enterprise Edition up to 17.4.5/17.5.3/17.6.1. It has been classified as problematic. This affects an unknown part of the component GraphQL Query Handler. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-863. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. This is going to have an impact on confidentiality. The summary by CVE is:

An issue has been discovered in GitLab CE/EE affecting all versions from 16.9 before 17.4.6, 17.5 before 17.5.4, and 17.6 before 17.6.2. By using a specific GraphQL query, under specific conditions an unauthorized user can retrieve branch names.

The weakness was released by shells3c as 480509. The advisory is shared at gitlab.com. This vulnerability is uniquely identified as CVE-2024-8116 since 08/23/2024. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 213030 (GitLab 16.9 < 17.4.6 / 17.5 < 17.5.4 / 17.6 < 17.6.2 (CVE-2024-8116)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 17.4.6, 17.5.4 or 17.6.2 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (213030). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Bug Tracking Software

Vendor

• GitLab

Name

• Community Edition
• Enterprise Edition

Version

• 17.4.0
• 17.4.1
• 17.4.2
• 17.4.3
• 17.4.4
• 17.4.5
• 17.5.0
• 17.5.1
• 17.5.2
• 17.5.3
• 17.6.0
• 17.6.1

License

• open-source

Website

• Vendor: https://gitlab.com/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion