GitLab Enterprise Edition up to 17.1.6/17.2.4/17.3.1 Group Member privilege defined with unsafe actions
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in GitLab Enterprise Edition up to 17.1.6/17.2.4/17.3.1. It has been classified as problematic. The impacted element is an unknown function of the component Group Member Handler. Performing a manipulation results in privilege defined with unsafe actions. This vulnerability is reported as CVE-2024-8631. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is recommended.
Details
A vulnerability classified as problematic has been found in GitLab Enterprise Edition up to 17.1.6/17.2.4/17.3.1. This affects an unknown code block of the component Group Member Handler. The manipulation with an unknown input leads to a privilege defined with unsafe actions vulnerability. CWE is classifying the issue as CWE-267. A particular privilege, role, capability, or right can be used to perform unsafe actions that were not intended, even when it is assigned to the correct entity. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
A privilege escalation issue has been discovered in GitLab EE affecting all versions starting from 16.6 prior to 17.1.7, from 17.2 prior to 17.2.5, and from 17.3 prior to 17.3.2. A user assigned the Admin Group Member custom role could have escalated their privileges to include other custom roles.
The weakness was disclosed by chotebabume as 462665. The advisory is shared at gitlab.com. This vulnerability is uniquely identified as CVE-2024-8631 since 09/09/2024. The exploitability is told to be easy. 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.
Upgrading to version 17.1.7, 17.2.5 or 17.3.2 eliminates this vulnerability.
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: 5.8VulDB Meta Temp Score: 5.7
VulDB Base Score: 4.7
VulDB Temp Score: 4.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.2
NVD Vector: 🔍
CNA Base Score: 5.5
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: Privilege defined with unsafe actionsCWE: CWE-267 / 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: Enterprise Edition 17.1.7/17.2.5/17.3.2
Timeline
09/09/2024 🔍09/12/2024 🔍
09/12/2024 🔍
09/14/2024 🔍
Sources
Vendor: gitlab.comAdvisory: 462665
Researcher: chotebabume
Status: Confirmed
CVE: CVE-2024-8631 (🔍)
GCVE (CVE): GCVE-0-2024-8631
GCVE (VulDB): GCVE-100-277317
Entry
Created: 09/12/2024 19:45Updated: 09/14/2024 17:59
Changes: 09/12/2024 19:45 (66), 09/14/2024 17:59 (12)
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.