Restricted artifact disclosure via browse and raw routes
Published Jul 25, 2024 · Updated Aug 29, 2024
GitLab CE/EE 16.7 through 17.0.4, 17.1 through 17.1.2, and 17.2.0 allows remote authenticated users to read restricted job artifacts. The artifact browse and raw routes omit the access check enforced by the normal download route, so they serve files marked for Developer access. Guest or Reporter membership in a project with a protected artifact is sufficient to disclose that artifact; no write or service-interruption impact is reported.
Summary
What happened
GitLab CE/EE 16.7 through 17.0.4, 17.1 through 17.1.2, and 17.2.0 allows remote authenticated users to read restricted job artifacts. The artifact browse and raw routes omit the access check enforced by the normal download route, so they serve files marked for Developer access. Guest or Reporter membership in a project with a protected artifact is sufficient to disclose that artifact; no write or service-interruption impact is reported.
The record
- CVE
- CVE-2024-7057
- Published
- Jul 25, 2024
- Updated
- Aug 29, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-284, T1213.003
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 25, 2024CVE publishedPublication date reported by the CVE source.
- Aug 29, 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=16.7 <17.0.5
- Affected versionversion=17.1 <17.1.3
- Affected versionversion=17.2 <17.2.1
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
- GitLab artifact access-bypass reproductionproof of concept · demonstrated
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