GitLab Community Edition/Enterprise Edition up to 15.0.4/15.1.3/15.2.0 2FA Enforcement improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in GitLab Community Edition and Enterprise Edition up to 15.0.4/15.1.3/15.2.0. It has been rated as critical. This vulnerability affects unknown code of the component 2FA Enforcement. This manipulation causes improper authentication. This vulnerability is handled as CVE-2022-2303. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is advised.
Details
A vulnerability has been found in GitLab Community Edition and Enterprise Edition up to 15.0.4/15.1.3/15.2.0 (Bug Tracking Software) and classified as critical. Affected by this vulnerability is an unknown function of the component 2FA Enforcement. The manipulation with an unknown input leads to a improper authentication vulnerability. The CWE definition for the vulnerability is CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
An issue has been discovered in GitLab CE/EE affecting all versions before 15.0.5, all versions starting from 15.1 before 15.1.4, all versions starting from 15.2 before 15.2.1. It may be possible for group members to bypass 2FA enforcement enabled at the group level by using Resource Owner Password Credentials grant to obtain an access token without using 2FA.
The weakness was released 08/05/2022 as 35502. The advisory is shared at gitlab.com. This vulnerability is known as CVE-2022-2303 since 07/04/2022. Neither technical details nor an exploit are publicly available.
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: 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: 🔍
Exploiting
Class: Improper authenticationCWE: 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: Community Edition/Enterprise Edition 15.0.5/15.1.4/15.2.1
Timeline
07/04/2022 🔍08/05/2022 🔍
08/05/2022 🔍
08/05/2022 🔍
Sources
Vendor: gitlab.comAdvisory: 35502
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2022-2303 (🔍)
GCVE (CVE): GCVE-0-2022-2303
GCVE (VulDB): GCVE-100-205681
Entry
Created: 08/05/2022 21:19Changes: 08/05/2022 21:19 (53)
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.