GitLab Enterprise Edition up to 15.0.4/15.1.3/15.2.0 access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in GitLab Enterprise Edition up to 15.0.4/15.1.3/15.2.0. This affects an unknown part. Performing a manipulation results in access control. This vulnerability was named CVE-2022-2501. The attack may be initiated remotely. There is no available exploit. It is suggested to upgrade the affected component.
Details
A vulnerability classified as problematic has been found in GitLab Enterprise Edition up to 15.0.4/15.1.3/15.2.0 (Bug Tracking Software). This affects an unknown code. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. This is going to have an impact on confidentiality. The summary by CVE is:
An improper access control issue in GitLab EE affecting all versions from 12.0 prior to 15.0.5, 15.1 prior to 15.1.4, and 15.2 prior to 15.2.1 allows an attacker to bypass IP allow-listing and download artifacts. This attack only bypasses IP allow-listing, proper permissions are still required.
The weakness was presented 08/05/2022 as 36482. The advisory is shared at gitlab.com. This vulnerability is uniquely identified as CVE-2022-2501 since 07/21/2022. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
Upgrading to version 15.0.5, 15.1.4 or 15.2.1 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.8VulDB Meta Temp Score: 4.7
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 5.9
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: Access controlCWE: CWE-284 / 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 15.0.5/15.1.4/15.2.1
Timeline
07/21/2022 🔍08/05/2022 🔍
08/05/2022 🔍
08/05/2022 🔍
Sources
Vendor: gitlab.comAdvisory: 36482
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2022-2501 (🔍)
GCVE (CVE): GCVE-0-2022-2501
GCVE (VulDB): GCVE-100-205713
Entry
Created: 08/05/2022 21:55Changes: 08/05/2022 21:55 (52)
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.