GitLab up to 13.1.9/13.2.7/13.3.3 Command Line privileges management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in GitLab up to 13.1.9/13.2.7/13.3.3. It has been classified as critical. This affects an unknown part of the component Command Line. Performing a manipulation results in privileges management. This vulnerability is cataloged as CVE-2020-13316. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as critical, was found in GitLab up to 13.1.9/13.2.7/13.3.3 (Bug Tracking Software). This affects an unknown code block of the component Command Line. The manipulation with an unknown input leads to a privileges management vulnerability. CWE is classifying the issue as CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. GitLab was not validating a Deploy-Token and allowed a disabled repository be accessible via a git command line.
The weakness was shared 09/14/2020 (Website). The advisory is shared at gitlab.com. This vulnerability is uniquely identified as CVE-2020-13316 since 05/21/2020. It is possible to initiate the attack remotely. The requirement for exploitation is a authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
Upgrading to version 13.1.10, 13.2.8 or 13.3.4 eliminates this vulnerability.
The entries VDB-161231, VDB-161230, VDB-161228 and VDB-161227 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
- 13.1.0
- 13.1.1
- 13.1.2
- 13.1.3
- 13.1.4
- 13.1.5
- 13.1.6
- 13.1.7
- 13.1.8
- 13.1.9
- 13.2.0
- 13.2.1
- 13.2.2
- 13.2.3
- 13.2.4
- 13.2.5
- 13.2.6
- 13.2.7
- 13.3.0
- 13.3.1
- 13.3.2
- 13.3.3
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.7
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.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: 🔍
Exploiting
Class: Privileges managementCWE: CWE-269 / 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: GitLab 13.1.10/13.2.8/13.3.4
Timeline
05/21/2020 🔍09/14/2020 🔍
09/15/2020 🔍
09/15/2020 🔍
Sources
Advisory: gitlab.comStatus: Not defined
CVE: CVE-2020-13316 (🔍)
GCVE (CVE): GCVE-0-2020-13316
GCVE (VulDB): GCVE-100-161229
See also: 🔍
Entry
Created: 09/15/2020 08:39Updated: 09/15/2020 08:44
Changes: 09/15/2020 08:39 (39), 09/15/2020 08:44 (12)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.