Restricted analytics disclosure via forced browsing
Published Mar 26, 2021 · Updated Aug 3, 2024
Improper access control in GitLab 13.4 through 13.8.3 allows remote authenticated users to read restricted project analytics. Analytics navigation honors the Only Project Members setting, but direct requests to graph, insight, and code-review URLs bypass that visibility check. An authenticated nonmember must target a public project configured to restrict Analytics; the exposure is limited to analytics details.
Summary
What happened
Improper access control in GitLab 13.4 through 13.8.3 allows remote authenticated users to read restricted project analytics. Analytics navigation honors the Only Project Members setting, but direct requests to graph, insight, and code-review URLs bypass that visibility check. An authenticated nonmember must target a public project configured to restrict Analytics; the exposure is limited to analytics details.
The record
- CVE
- CVE-2021-22180
- Published
- Mar 26, 2021
- Updated
- Aug 3, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-425, T1213.003
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 26, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=>=13.6, <13.6.7
- Affected versionversion=>=13.7, <13.7.7
- Affected versionversion=>=13.8, <13.8.4
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
- Analytics visible to nonmember users despite Only Project Membersproof 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