Developer-level analytics settings disclosure via DOM exposure
Published Jul 24, 2024 · Updated Aug 29, 2024
Information disclosure in affected GitLab EE releases allows remote authenticated users to read project analytics settings from the DOM. GitLab has not published the specific view, serializer, or authorization check that placed those settings into client-visible markup. Reachability requires group membership with the Developer role or higher, and the reported consequence is confidentiality loss without data modification or service interruption.
Summary
What happened
Information disclosure in affected GitLab EE releases allows remote authenticated users to read project analytics settings from the DOM. GitLab has not published the specific view, serializer, or authorization check that placed those settings into client-visible markup. Reachability requires group membership with the Developer role or higher, and the reported consequence is confidentiality loss without data modification or service interruption.
The record
- CVE
- CVE-2024-5067
- Published
- Jul 24, 2024
- Updated
- Aug 29, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-200
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 24, 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.11 <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
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