GitLab Community Edition/Enterprise Edition up to 11.1.6/11.2.3/11.3.0 Sentry Log GRPC::Unknown information disclosure
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
4.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in GitLab Community Edition and Enterprise Edition up to 11.1.6/11.2.3/11.3.0. Affected is the function GRPC::Unknown
of the component Sentry Log. The manipulation leads to information disclosure.
This vulnerability is traded as CVE-2018-17453. There is no exploit available.
It is recommended to upgrade the affected component.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Details
A vulnerability, which was classified as problematic, has been found in GitLab Community Edition and Enterprise Edition up to 11.1.6/11.2.3/11.3.0 (Bug Tracking Software). This issue affects the function GRPC::Unknown
of the component Sentry Log. 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.1.7, 11.2.x before 11.2.4, and 11.3.x before 11.3.1. Attackers may have been able to obtain sensitive access-token data from Sentry logs via the GRPC::Unknown exception.
The weakness was disclosed 04/16/2023. It is possible to read the advisory at about.gitlab.com. The identification of this vulnerability is CVE-2018-17453 since 09/25/2018. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
Upgrading to version 11.1.7, 11.2.4 or 11.3.1 eliminates this vulnerability. The upgrade is hosted for download at about.gitlab.com.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.3
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Local: No
Remote: Partially
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.1.7/11.2.4/11.3.1
Timeline
09/25/2018 🔍04/16/2023 🔍
04/16/2023 🔍
05/05/2023 🔍
Sources
Vendor: gitlab.comAdvisory: about.gitlab.com
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2018-17453 (🔍)
GCVE (CVE): GCVE-0-2018-17453
GCVE (VulDB): GCVE-100-226127
Entry
Created: 04/16/2023 07:43 AMUpdated: 05/05/2023 11:01 AM
Changes: 04/16/2023 07:43 AM (44), 05/05/2023 11:01 AM (11)
Complete: 🔍
Cache ID: 18:012:40
No comments yet. Languages: en.
Please log in to comment.