CVE-2023-5117: Exposure of Sensitive Information Due to Incompatible Policies in GitLab
First published: Wed Dec 25 2024(Updated: )
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.
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab Community Edition | <17.6.0 |
Remedy
Upgrade to versions 17.6.0 or above.
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2023-5117?
CVE-2023-5117 is considered a high severity vulnerability due to the potential exposure of confidential information.
How do I fix CVE-2023-5117?
To fix CVE-2023-5117, upgrade GitLab CE/EE to version 17.6.0 or later.
Who is affected by CVE-2023-5117?
CVE-2023-5117 affects all versions of GitLab CE/EE prior to 17.6.0.
What are the risks associated with CVE-2023-5117?
The main risk associated with CVE-2023-5117 is unauthorized access to confidential files uploaded in comments on public project issues.
What should users do if they cannot upgrade GitLab due to CVE-2023-5117?
If upgrade is not possible, users should consider restricting access to public project issues or securely managing file uploads.
- agent/remedy
- agent/weakness
- agent/title
- agent/references
- agent/first-publish-date
- agent/description
- agent/type
- collector/nvd-api
- source/NVD
- agent/severity
- agent/author
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/source
- agent/softwarecombine
- agent/tags
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/gitlab
- canonical/gitlab community edition