GitLab Community Edition/Enterprise Edition up to 12.1.11/12.2.5/12.3.1 GraphQL Endpoint information disclosure
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in GitLab Community Edition and Enterprise Edition up to 12.1.11/12.2.5/12.3.1. Affected by this issue is some unknown functionality of the component GraphQL Endpoint. The manipulation leads to information disclosure. This vulnerability is handled as CVE-2019-15576. The attack may be launched remotely. There is no exploit available. It is recommended to upgrade the affected component. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Details
A vulnerability classified as problematic was found in GitLab Community Edition and Enterprise Edition up to 12.1.11/12.2.5/12.3.1 (Bug Tracking Software). Affected by this vulnerability is some unknown processing of the component GraphQL Endpoint. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:
An information disclosure vulnerability exists in GitLab CE/EE <v12.3.2, <v12.2.6, and <v12.1.12 that allowed an attacker to view private system notes from a GraphQL endpoint.
The weakness was published 12/18/2019. This vulnerability is known as CVE-2019-15576. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
Upgrading to version 12.1.12, 12.2.6 or 12.3.2 eliminates this vulnerability.
Similar entries are available at VDB-147479, VDB-147478, VDB-147477 and VDB-147476. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
- 12.1.0
- 12.1.1
- 12.1.2
- 12.1.3
- 12.1.4
- 12.1.5
- 12.1.6
- 12.1.7
- 12.1.8
- 12.1.9
- 12.1.10
- 12.1.11
- 12.2.0
- 12.2.1
- 12.2.2
- 12.2.3
- 12.2.4
- 12.2.5
- 12.3.0
- 12.3.1
License
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: 🔍
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 12.1.12/12.2.6/12.3.2
Timeline
08/26/2019 🔍12/18/2019 🔍
12/20/2019 🔍
03/15/2024 🔍
Sources
Vendor: gitlab.comAdvisory: hackerone.com
Status: Not defined
CVE: CVE-2019-15576 (🔍)
GCVE (CVE): GCVE-0-2019-15576
GCVE (VulDB): GCVE-100-147475
See also: 🔍
Entry
Created: 12/20/2019 06:28Updated: 03/15/2024 14:34
Changes: 12/20/2019 06:28 (38), 12/20/2019 06:33 (17), 03/15/2024 14:34 (5)
Complete: 🔍
Cache ID: 216:34D:103
No comments yet. Languages: en.
Please log in to comment.