GitLab Community Edition/Enterprise Edition up to 17.4.4/17.5.2/17.6.0 Personal Access Token authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in GitLab Community Edition and Enterprise Edition up to 17.4.4/17.5.2/17.6.0. Affected by this issue is some unknown functionality of the component Personal Access Token Handler. Executing a manipulation can lead to authorization. This vulnerability is registered as CVE-2024-8114. It is possible to launch the attack remotely. No exploit is available. It is advisable to upgrade the affected component.
Details
A vulnerability classified as problematic was found in GitLab Community Edition and Enterprise Edition up to 17.4.4/17.5.2/17.6.0. This vulnerability affects an unknown functionality of the component Personal Access Token Handler. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
An issue has been discovered in GitLab CE/EE affecting all versions from 8.12 before 17.4.5, 17.5 before 17.5.3, and 17.6 before 17.6.1. This issue allows an attacker with access to a victim's Personal Access Token (PAT) to escalate privileges.
The weakness was published by pwnie as 480494. The advisory is available at gitlab.com. This vulnerability was named CVE-2024-8114 since 08/23/2024. The exploitation appears to be difficult. The attack can be initiated remotely. The technical details are unknown and an exploit is not available.
The vulnerability scanner Nessus provides a plugin with the ID 211857 (GitLab 8.12 < 17.4.5 / 17.5 < 17.5.3 / 17.6 < 17.6.1 (CVE-2024-8114)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 17.4.5, 17.5.3 or 17.6.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (211857). If you want to get best quality of vulnerability data, you may have to visit 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: 6.6VulDB Meta Temp Score: 6.5
VulDB Base Score: 5.0
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 8.2
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: AuthorizationCWE: CWE-862 / CWE-863 / CWE-285
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: 211857
Nessus Name: GitLab 8.12 < 17.4.5 / 17.5 < 17.5.3 / 17.6 < 17.6.1 (CVE-2024-8114)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Community Edition/Enterprise Edition 17.4.5/17.5.3/17.6.1
Timeline
08/23/2024 🔍11/26/2024 🔍
11/27/2024 🔍
11/27/2024 🔍
Sources
Vendor: gitlab.comAdvisory: 480494
Researcher: pwnie
Status: Confirmed
CVE: CVE-2024-8114 (🔍)
GCVE (CVE): GCVE-0-2024-8114
GCVE (VulDB): GCVE-100-286210
Entry
Created: 11/27/2024 00:18Updated: 11/27/2024 04:03
Changes: 11/27/2024 00:18 (66), 11/27/2024 04:03 (2)
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.