Private analytics disclosure via insufficient role check
Published Mar 6, 2025 · Updated Mar 6, 2025
Improper authorization in affected GitLab EE 17.7–17.9 releases allows remote authenticated users to read private-project analytics. The /analytics/code_reviews route accepts Planner-role membership even though private-project code review analytics require Reporter or higher access. A Planner role on a private Ultimate project is required; exposure is limited to code review analytics, with no write or service impact.
Summary
What happened
Improper authorization in affected GitLab EE 17.7–17.9 releases allows remote authenticated users to read private-project analytics. The /analytics/code_reviews route accepts Planner-role membership even though private-project code review analytics require Reporter or higher access. A Planner role on a private Ultimate project is required; exposure is limited to code review analytics, with no write or service impact.
The record
- CVE
- CVE-2025-2045
- Published
- Mar 6, 2025
- Updated
- Mar 6, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-863, T1213.003
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 6, 2025CVE publishedPublication date reported by the CVE source.
- Mar 6, 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=17.7.0 <17.7.6
- Affected versionversion=17.8 <17.8.4
- Affected versionversion=17.9 <17.9.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
- Planner-role code review analytics 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