GitLab Enterprise Edition up to 17.0.5/17.1.3/17.2.1 Policy authentication bypass
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in GitLab Enterprise Edition up to 17.0.5/17.1.3/17.2.1 and classified as problematic. This vulnerability affects unknown code of the component Policy Handler. Performing a manipulation results in authentication bypass. This vulnerability is cataloged as CVE-2024-4784. It is possible to initiate the attack remotely. There is no exploit available. The affected component should be upgraded.
Details
A vulnerability classified as problematic has been found in GitLab Enterprise Edition up to 17.0.5/17.1.3/17.2.1. This affects an unknown part of the component Policy Handler. The manipulation with an unknown input leads to a authentication bypass vulnerability. CWE is classifying the issue as CWE-305. The authentication algorithm is sound, but the implemented mechanism can be bypassed as the result of a separate weakness that is primary to the authentication error. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
An issue was discovered in GitLab EE starting from version 16.7 before 17.0.6, version 17.1 before 17.1.4 and 17.2 before 17.2.2 that allowed bypassing the password re-entry requirement to approve a policy.
The weakness was shared by vexin as 461248. The advisory is shared at gitlab.com. This vulnerability is uniquely identified as CVE-2024-4784 since 05/10/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 17.0.6, 17.1.4 or 17.2.2 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best 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: 4.9VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.0
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.4
NVD Vector: 🔍
CNA Base Score: 4.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: Authentication bypassCWE: CWE-305 / CWE-287
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.0.6/17.1.4/17.2.2
Timeline
05/10/2024 🔍08/08/2024 🔍
08/08/2024 🔍
08/24/2024 🔍
Sources
Vendor: gitlab.comAdvisory: 461248
Researcher: vexin
Status: Confirmed
CVE: CVE-2024-4784 (🔍)
GCVE (CVE): GCVE-0-2024-4784
GCVE (VulDB): GCVE-100-273969
Entry
Created: 08/08/2024 13:18Updated: 08/24/2024 07:07
Changes: 08/08/2024 13:18 (66), 08/24/2024 07:07 (13)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.