CVE-2023-5117 Exposure of Sensitive Information Due to Incompatible Policies in GitLab
Attackers can access files uploaded to comments on confidential issues in public projects without authentication via direct links.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2023-5117?
CVE-2023-5117 is a low-severity vulnerability in Gitlab Gitlab, published on 25 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-213
Which versions are affected by CVE-2023-5117?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | All versions | 17.6.0 |
Products include Gitlab Gitlab.
How do I fix CVE-2023-5117?
Upgrade gitlab to 17.6.0 or later.
Is CVE-2023-5117 being exploited?
There is no known exploitation of CVE-2023-5117 in the wild and no public exploit code.
Other vulnerabilities in Gitlab Gitlab
- CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound
- CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)
Sources
Also known as BIT-gitlab-2023-5117, GHSA-pwvw-rggj-f74r, UBUNTU-CVE-2023-5117.