GitLab Community Edition/Enterprise Edition up to 17.5.x unnecessary privileges
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in GitLab Community Edition and Enterprise Edition up to 17.5.x. This affects an unknown function. Performing a manipulation results in unnecessary privileges. This vulnerability is reported as CVE-2024-8266. The attack is possible to be carried out remotely. No exploit exists. It is suggested to upgrade the affected component.
Details
A vulnerability classified as problematic has been found in GitLab Community Edition and Enterprise Edition up to 17.5.x. This affects an unknown code. The manipulation with an unknown input leads to a unnecessary privileges vulnerability. CWE is classifying the issue as CWE-250. The product performs an operation at a privilege level that is higher than the minimum level required, which creates new weaknesses or amplifies the consequences of other weaknesses. This is going to have an impact on integrity. The summary by CVE is:
An issue was discovered in GitLab CE/EE affecting all versions starting from 17.1 prior to 17.6.0, which allows an attacker with maintainer role to trigger a pipeline as project owner under certain circumstances.
The weakness was disclosed by pwnie as 481531. The advisory is shared at gitlab.com. This vulnerability is uniquely identified as CVE-2024-8266 since 08/28/2024. The exploitability is told to be difficult. It is possible to initiate the attack remotely. Additional levels of successful authentication are required for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 253576 (Linux Distros Unpatched Vulnerability : CVE-2024-8266), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 17.6.0 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (253576). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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: 4.4VulDB Meta Temp Score: 4.4
VulDB Base Score: 2.2
VulDB Temp Score: 2.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.6
NVD Vector: 🔍
CNA Base Score: 4.4
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: Unnecessary privilegesCWE: CWE-250
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 |
Nessus ID: 253576
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2024-8266
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Community Edition/Enterprise Edition 17.6.0
Timeline
08/28/2024 🔍02/13/2025 🔍
02/13/2025 🔍
08/22/2025 🔍
Sources
Vendor: gitlab.comAdvisory: 481531
Researcher: pwnie
Status: Confirmed
CVE: CVE-2024-8266 (🔍)
GCVE (CVE): GCVE-0-2024-8266
GCVE (VulDB): GCVE-100-295677
Entry
Created: 02/13/2025 08:09Updated: 08/22/2025 18:28
Changes: 02/13/2025 08:09 (65), 08/06/2025 22:18 (12), 08/22/2025 18:28 (2)
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.