CVE-2023-5117 | Exposure of Sensitive Information Due to Incompatible Policies in GitLab

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.

Published: 2024-12-25 Last update: 2025-07-11 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-5117 is rated Low Risk (22.3/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.30%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2023-5117

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.18% 0.30% +0.11%
2 2026-05-16 0.12% 0.18% +0.06%
3 2026-02-02 — 0.12% —

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-5117

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.7 3.1 LOW
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.2 1.4 [email protected]

Weakness enumeration for CVE-2023-5117

OS Trackers for CVE-2023-5117

vendor priority summary link
debian not yet assigned CVE-2023-5117 not yet assigned priority: Debian including 1 source packages (gitlab), 1 status rows across 1 suites (sid): resolved 1. https://security-tracker.debian.org/tracker/CVE-2023-5117
ubuntu medium CVE-2023-5117 medium priority: Ubuntu including 1 source packages (gitlab), 6 status rows across 6 suites (focal, jammy, noble, oracular, upstream, xenial): DNE 4, ignored 1, needs-triage 1. https://ubuntu.com/security/CVE-2023-5117

Affected software / configurations for CVE-2023-5117

Vendor Product Version Raw CPE
gitlab gitlab < 17.6.0 cpe:2.3:a:gitlab:gitlab:*:*:*:*:community:*:*:*
gitlab gitlab < 17.6.0 cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*

References for CVE-2023-5117

URL Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/398250 Issue Tracking Vendor Advisory
cvelogic Threat Intelligence