Gitaly up to 13.3.8/13.4.4/13.5.1 Import information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Gitaly up to 13.3.8/13.4.4/13.5.1. Affected by this vulnerability is an unknown functionality of the component Import Handler. Performing a manipulation results in information disclosure. This vulnerability was named CVE-2020-13353. The attack needs to be approached locally. There is no available exploit. It is advisable to upgrade the affected component.
Details
A vulnerability classified as problematic has been found in Gitaly up to 13.3.8/13.4.4/13.5.1. This affects an unknown functionality of the component Import Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality.
The weakness was presented 11/17/2020. The advisory is shared at gitlab.com. This vulnerability is uniquely identified as CVE-2020-13353. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
Upgrading to version 13.3.9, 13.4.5 or 13.5.2 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.5VulDB Meta Temp Score: 2.5
VulDB Base Score: 1.9
VulDB Temp Score: 1.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 3.2
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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: Gitaly 13.3.9/13.4.5/13.5.2
Timeline
05/21/2020 🔍11/17/2020 🔍
11/17/2020 🔍
12/08/2020 🔍
Sources
Advisory: gitlab.comStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2020-13353 (🔍)
GCVE (CVE): GCVE-0-2020-13353
GCVE (VulDB): GCVE-100-165033
Entry
Created: 11/17/2020 08:56Updated: 12/08/2020 08:07
Changes: 11/17/2020 08:56 (38), 12/08/2020 08:00 (3), 12/08/2020 08:07 (19)
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.