GitLab Community Edition/Enterprise Edition up to 14.10.4/15.0.3/15.1.0 Error Tracking improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in GitLab Community Edition and Enterprise Edition up to 14.10.4/15.0.3/15.1.0. The affected element is an unknown function of the component Error Tracking Handler. Performing a manipulation results in improper authorization. This vulnerability is identified as CVE-2022-2244. The attack can be initiated remotely. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability classified as critical has been found in GitLab Community Edition and Enterprise Edition up to 14.10.4/15.0.3/15.1.0 (Bug Tracking Software). This affects some unknown functionality of the component Error Tracking Handler. The manipulation with an unknown input leads to a improper authorization vulnerability. CWE is classifying the issue as CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
An improper authorization vulnerability in GitLab EE/CE affecting all versions from 14.8 prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1, allows project memebers with reporter role to manage issues in project's error tracking feature.
The weakness was released 07/02/2022 as 36066. The advisory is shared at gitlab.com. This vulnerability is uniquely identified as CVE-2022-2244 since 06/28/2022. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1548.002 for this issue.
Upgrading to version 14.10.5, 15.0.4 or 15.1.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: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 4.3
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Improper authorizationCWE: 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 14.10.5/15.0.4/15.1.1
Timeline
06/28/2022 🔍07/02/2022 🔍
07/02/2022 🔍
07/18/2022 🔍
Sources
Vendor: gitlab.comAdvisory: 36066
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2022-2244 (🔍)
GCVE (CVE): GCVE-0-2022-2244
GCVE (VulDB): GCVE-100-203121
Entry
Created: 07/02/2022 08:54Updated: 07/18/2022 09:32
Changes: 07/02/2022 08:54 (53), 07/18/2022 09:32 (7)
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.