GitLab Community/Enterprise up to 11.6.9/11.7.5/11.8.0 information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in GitLab Community and Enterprise up to 11.6.9/11.7.5/11.8.0. It has been rated as problematic. The affected element is an unknown function. The manipulation leads to information disclosure. This vulnerability is traded as CVE-2019-9223. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is advised.
Details
A vulnerability was found in GitLab Community and Enterprise up to 11.6.9/11.7.5/11.8.0 (Bug Tracking Software). It has been rated as problematic. This issue affects an unknown function. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:
An issue was discovered in GitLab Community and Enterprise Edition before 11.6.10, 11.7.x before 11.7.6, and 11.8.x before 11.8.1. It allows Information Exposure.
The weakness was shared 04/17/2019 (Website). The advisory is shared at about.gitlab.com. The identification of this vulnerability is CVE-2019-9223 since 02/28/2019. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
The commercial vulnerability scanner Qualys is able to test this issue with plugin 371751 (GitLab Multiple Security Vulnerability).
Upgrading to version 11.6.10, 11.7.6 or 11.8.1 eliminates this vulnerability.
The entries VDB-133457, VDB-133458, VDB-133459 and VDB-133460 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
Vendor
Name
Version
- 11.0
- 11.1
- 11.2
- 11.3
- 11.4
- 11.5
- 11.6
- 11.6.0
- 11.6.1
- 11.6.2
- 11.6.3
- 11.6.4
- 11.6.5
- 11.6.6
- 11.6.7
- 11.6.8
- 11.6.9
- 11.7
- 11.7.0
- 11.7.1
- 11.7.2
- 11.7.3
- 11.7.4
- 11.7.5
- 11.8.0
License
Website
- Vendor: https://gitlab.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: 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 |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Community/Enterprise 11.6.10/11.7.6/11.8.1
Timeline
02/28/2019 🔍04/17/2019 🔍
04/17/2019 🔍
08/29/2023 🔍
Sources
Vendor: gitlab.comAdvisory: 50334
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2019-9223 (🔍)
GCVE (CVE): GCVE-0-2019-9223
GCVE (VulDB): GCVE-100-133469
See also: 🔍
Entry
Created: 04/17/2019 23:23Updated: 08/29/2023 16:17
Changes: 04/17/2019 23:23 (59), 05/30/2020 11:18 (1), 08/29/2023 16:17 (4)
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.