Branch-name disclosure via disabled repository access
Published Apr 24, 2025 · Updated Apr 24, 2025
Information disclosure in GitLab EE allows remote authenticated users to view branch names when repository features are disabled. Project access controls return branch-name metadata without enforcing the disabled state of Repository and its related assets. The affected ranges are 17.7 through 17.9.6, 17.10 through 17.10.4, and 17.11.0; disclosure is limited to branch names.
Summary
What happened
Information disclosure in GitLab EE allows remote authenticated users to view branch names when repository features are disabled. Project access controls return branch-name metadata without enforcing the disabled state of Repository and its related assets. The affected ranges are 17.7 through 17.9.6, 17.10 through 17.10.4, and 17.11.0; disclosure is limited to branch names.
The record
- CVE
- CVE-2024-12244
- Published
- Apr 24, 2025
- Updated
- Apr 24, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-862, T1213.003
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 24, 2025CVE publishedPublication date reported by the CVE source.
- Apr 24, 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.10 <17.10.5
- Affected versionversion=17.11 <17.11.1
- Affected versionversion=17.7 <17.9.7
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