GitLab Community Edition/Enterprise Edition up to 11.2.1 information disclosure
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
5.3 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in GitLab Community Edition and Enterprise Edition up to 11.2.1 and classified as problematic. Affected by this vulnerability is an unknown functionality. The manipulation leads to information disclosure. This vulnerability is known as CVE-2018-16051. The attack can be launched remotely. There is no exploit available. It is recommended to upgrade the affected component. VulDB is the best source for vulnerability data and more expert information about this specific topic.
Details
A vulnerability, which was classified as problematic, was found in GitLab Community Edition and Enterprise Edition up to 11.2.1 (Bug Tracking Software). Affected is an unknown code block. 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. CVE summarizes:
An issue was discovered in GitLab Community and Enterprise Edition before 11.0.6, 11.1.x before 11.1.5, and 11.2.x before 11.2.2. There is Orphaned Upload Files Exposure.
The bug was discovered 08/28/2018. The weakness was disclosed 10/03/2018 (Website). The advisory is shared for download at about.gitlab.com. This vulnerability is traded as CVE-2018-16051 since 08/28/2018. The exploitability is told to be easy. It is possible to launch the attack remotely. The requirement for exploitation is a authentication. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1592.
The vulnerability was handled as a non-public zero-day exploit for at least 36 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 11.0.6, 11.1.5 or 11.2.2 eliminates this vulnerability.
The entries VDB-124749, VDB-124750 and VDB-124751 are pretty similar. VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.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: 🔍
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 11.0.6/11.1.5/11.2.2
Timeline
08/28/2018 🔍08/28/2018 🔍
10/03/2018 🔍
10/03/2018 🔍
10/04/2018 🔍
05/22/2023 🔍
Sources
Vendor: gitlab.comAdvisory: 6012
Status: Not defined
Confirmation: 🔍
CVE: CVE-2018-16051 (🔍)
GCVE (CVE): GCVE-0-2018-16051
GCVE (VulDB): GCVE-100-124752
See also: 🔍
Entry
Created: 10/04/2018 07:54 AMUpdated: 05/22/2023 08:05 AM
Changes: 10/04/2018 07:54 AM (60), 03/29/2020 02:05 PM (2), 05/22/2023 08:05 AM (4)
Complete: 🔍
Cache ID: 18:EB9:40
No comments yet. Languages: en.
Please log in to comment.