Unauthenticated attachment disclosure via project-level access policy
Published Dec 25, 2024 · Updated Dec 26, 2024
Information disclosure in GitLab CE/EE before 17.6.0 allows remote attackers to read confidential attachments through direct URLs. The upload-serving path applies public project or group visibility instead of the confidentiality policy of the parent issue or epic. An attacker must obtain the randomized 32-character upload URL; disclosure is limited to the referenced file, with no reported write access.
Summary
What happened
Information disclosure in GitLab CE/EE before 17.6.0 allows remote attackers to read confidential attachments through direct URLs. The upload-serving path applies public project or group visibility instead of the confidentiality policy of the parent issue or epic. An attacker must obtain the randomized 32-character upload URL; disclosure is limited to the referenced file, with no reported write access.
The record
- CVE
- CVE-2023-5117
- Published
- Dec 25, 2024
- Updated
- Dec 26, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-213, T1213
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 25, 2024CVE publishedPublication date reported by the CVE source.
- Dec 26, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <17.6.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo