GitLab Community Edition 13.7 Redis credentials storage
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in GitLab Community Edition 13.7. Impacted is an unknown function of the component Redis. Performing a manipulation results in credentials storage. This vulnerability is identified as CVE-2021-22194. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability classified as problematic has been found in GitLab Community Edition 13.7 (Bug Tracking Software). This affects some unknown processing of the component Redis. The manipulation with an unknown input leads to a credentials storage vulnerability. CWE is classifying the issue as CWE-256. Storing a password in plaintext may result in a system compromise. This is going to have an impact on confidentiality.
The weakness was released 03/27/2021. It is possible to read the advisory at gitlab.com. This vulnerability is uniquely identified as CVE-2021-22194. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1552 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for 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: 3.3VulDB Meta Temp Score: 3.3
VulDB Base Score: 2.2
VulDB Temp Score: 2.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.4
NVD Vector: 🔍
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: Credentials storageCWE: CWE-256 / CWE-255
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/05/2021 🔍03/27/2021 🔍
03/27/2021 🔍
04/06/2021 🔍
Sources
Vendor: gitlab.comAdvisory: gitlab.com
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2021-22194 (🔍)
GCVE (CVE): GCVE-0-2021-22194
GCVE (VulDB): GCVE-100-171891
Entry
Created: 03/27/2021 11:42Updated: 04/06/2021 09:24
Changes: 03/27/2021 11:42 (37), 04/06/2021 09:20 (3), 04/06/2021 09:24 (19)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.