Repository disclosure via undisclosed object authorization failure
Published Feb 12, 2025 · Updated Feb 12, 2025
An IDOR in GitLab EE 15.7 through 17.6.4, 17.7 through 17.7.3, and 17.8 through 17.8.1 lets remote authenticated users view repositories. GitLab has not publicly identified the request handler or missing authorization check that permits a repository object to be retrieved. High-privilege access is required, and the reported consequence is unauthorized repository viewing without integrity or availability impact.
Summary
What happened
An IDOR in GitLab EE 15.7 through 17.6.4, 17.7 through 17.7.3, and 17.8 through 17.8.1 lets remote authenticated users view repositories. GitLab has not publicly identified the request handler or missing authorization check that permits a repository object to be retrieved. High-privilege access is required, and the reported consequence is unauthorized repository viewing without integrity or availability impact.
The record
- CVE
- CVE-2025-1042
- Published
- Feb 12, 2025
- Updated
- Feb 12, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-552, T1213.003
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 12, 2025CVE publishedPublication date reported by the CVE source.
- Feb 12, 2025Record 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=15.7 <17.6.5
- Affected versionversion=17.7 <17.7.4
- Affected versionversion=17.8 <17.8.2
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