GitLab Community Edition/Enterprise Edition up to 17.1.6/17.2.4/17.3.1 Group Member authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.5 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in GitLab Community Edition and Enterprise Edition up to 17.1.6/17.2.4/17.3.1. Impacted is an unknown function of the component Group Member Handler. Performing a manipulation results in authorization. This vulnerability is known as CVE-2024-6685. Remote exploitation of the attack is possible. No exploit is available. You should upgrade the affected component.
Details
A vulnerability was found in GitLab Community Edition and Enterprise Edition up to 17.1.6/17.2.4/17.3.1. It has been classified as problematic. This affects some unknown functionality of the component Group Member 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. The summary by CVE is:
An issue was discovered in GitLab CE/EE affecting all versions starting from 16.7 prior to 17.1.7, 17.2 prior to 17.2.5, and 17.3 prior to 17.3.2, where group runners information was disclosed to unauthorised group members.
The weakness was published by ashish_r_padelkar as 472012. It is possible to read the advisory at gitlab.com. This vulnerability is uniquely identified as CVE-2024-6685 since 07/11/2024. The exploitability is told to be difficult. It is possible to initiate the attack remotely. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 17.1.7, 17.2.5 or 17.3.2 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
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: 3.5VulDB Meta Temp Score: 3.5
VulDB Base Score: 3.1
VulDB Temp Score: 3.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.3
NVD Vector: 🔍
CNA Base Score: 3.1
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-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: Community Edition/Enterprise Edition 17.1.7/17.2.5/17.3.2
Timeline
07/11/2024 🔍09/17/2024 🔍
09/17/2024 🔍
09/24/2024 🔍
Sources
Vendor: gitlab.comAdvisory: 472012
Researcher: ashish_r_padelkar
Status: Confirmed
CVE: CVE-2024-6685 (🔍)
GCVE (CVE): GCVE-0-2024-6685
GCVE (VulDB): GCVE-100-277755
Entry
Created: 09/17/2024 08:19Updated: 09/24/2024 20:22
Changes: 09/17/2024 08:19 (66), 09/20/2024 20:27 (1), 09/24/2024 20:22 (11)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.