GitLab Community Edition/Enterprise Edition up to 13.3.8/13.4.4/13.5.1 Project Maintainer state issue
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in GitLab Community Edition and Enterprise Edition up to 13.3.8/13.4.4/13.5.1. It has been rated as problematic. This affects an unknown part of the component Project Maintainer Handler. Performing a manipulation results in state issue. This vulnerability was named CVE-2020-13359. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is advised.
Details
A vulnerability classified as problematic has been found in GitLab Community Edition and Enterprise Edition up to 13.3.8/13.4.4/13.5.1 (Bug Tracking Software). This affects an unknown function of the component Project Maintainer Handler. The manipulation with an unknown input leads to a state issue vulnerability. CWE is classifying the issue as CWE-371. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was presented 11/19/2020. It is possible to read the advisory at gitlab.com. This vulnerability is uniquely identified as CVE-2020-13359. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 13.3.9, 13.4.5 or 13.5.2 eliminates this vulnerability.
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: 4.7VulDB Meta Temp Score: 4.5
VulDB Base Score: 4.7
VulDB Temp Score: 4.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: State issueCWE: CWE-371
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 13.3.9/13.4.5/13.5.2
Timeline
05/21/2020 🔍11/19/2020 🔍
11/19/2020 🔍
12/08/2020 🔍
Sources
Vendor: gitlab.comAdvisory: gitlab.com
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2020-13359 (🔍)
GCVE (CVE): GCVE-0-2020-13359
GCVE (VulDB): GCVE-100-165123
Entry
Created: 11/19/2020 06:45Updated: 12/08/2020 21:29
Changes: 11/19/2020 06:45 (39), 12/08/2020 21:26 (5), 12/08/2020 21:29 (8)
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.