GitLab Community Edition/Enterprise Edition up to 17.5.x exposure of sensitive information
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.6 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in GitLab Community Edition and Enterprise Edition up to 17.5.x. This issue affects some unknown processing. Performing a manipulation results in exposure of sensitive information. This vulnerability was named CVE-2023-5117. The attack may be initiated remotely. There is no available exploit. It is suggested to upgrade the affected component.
Details
A vulnerability was found in GitLab Community Edition and Enterprise Edition up to 17.5.x. It has been classified as problematic. This affects an unknown code. The manipulation with an unknown input leads to a exposure of sensitive information vulnerability. CWE is classifying the issue as CWE-213. The product's intended functionality exposes information to certain actors in accordance with the developer's security policy, but this information is regarded as sensitive according to the intended security policies of other stakeholders such as the product's administrator, users, or others whose information is being processed. This is going to have an impact on confidentiality. The summary by CVE is:
An issue was discovered in GitLab CE/EE affecting all versions before 17.6.0 in which users were unaware that files uploaded to comments on confidential issues and epics of public projects could be accessed without authentication via a direct link to the uploaded file URL.
The weakness was presented by Greg Myers. The advisory is shared at gitlab.com. This vulnerability is uniquely identified as CVE-2023-5117 since 09/22/2023. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
Upgrading to version 17.6.0 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://gitlab.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.7VulDB Meta Temp Score: 3.7
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 3.7
CNA Vector (GitLab): 🔍
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: Exposure of sensitive informationCWE: CWE-213 / CWE-200 / CWE-284
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Community Edition/Enterprise Edition 17.6.0
Timeline
09/22/2023 🔍12/25/2024 🔍
12/25/2024 🔍
07/12/2025 🔍
Sources
Vendor: gitlab.comAdvisory: gitlab.com
Researcher: Greg Myers
Status: Confirmed
CVE: CVE-2023-5117 (🔍)
GCVE (CVE): GCVE-0-2023-5117
GCVE (VulDB): GCVE-100-289293
Entry
Created: 12/25/2024 16:11Updated: 07/12/2025 10:07
Changes: 12/25/2024 16:11 (64), 07/12/2025 10:07 (1)
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.