GitLab up to 16.10.5/16.11.2/17.0.0 Naming Convention authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.5 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in GitLab up to 16.10.5/16.11.2/17.0.0. This affects an unknown part of the component Naming Convention Handler. Performing a manipulation results in authorization. This vulnerability is reported as CVE-2024-5258. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.
Details
A vulnerability was found in GitLab up to 16.10.5/16.11.2/17.0.0. It has been classified as problematic. This affects some unknown functionality of the component Naming Convention Handler. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
An authorization vulnerability exists within GitLab from versions 16.10 before 16.10.6, 16.11 before 16.11.3, and 17.0 before 17.0.1 where an authenticated attacker could utilize a crafted naming convention to bypass pipeline authorization logic.
The weakness was disclosed by Andrew Winata as 443254. The advisory is shared at gitlab.com. This vulnerability is uniquely identified as CVE-2024-5258 since 05/23/2024. The exploitability is told to be difficult. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available.
Upgrading to version 16.10.6, 16.11.3 or 17.0.1 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.6VulDB Meta Temp Score: 4.5
VulDB Base Score: 5.0
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.3
NVD Vector: 🔍
CNA Base Score: 4.4
CNA Vector (GitLab Inc.): 🔍
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-639 / CWE-285 / CWE-266
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: GitLab 16.10.6/16.11.3/17.0.1
Timeline
05/23/2024 🔍05/23/2024 🔍
05/23/2024 🔍
12/13/2024 🔍
Sources
Advisory: 443254Researcher: Andrew Winata
Status: Confirmed
CVE: CVE-2024-5258 (🔍)
GCVE (CVE): GCVE-0-2024-5258
GCVE (VulDB): GCVE-100-266037
Entry
Created: 05/23/2024 14:29Updated: 12/13/2024 20:07
Changes: 05/23/2024 14:29 (65), 12/13/2024 20:07 (13)
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.