Default branch disclosure via project-page metadata
Published Dec 13, 2021 · Updated Aug 4, 2024
Information disclosure in GitLab CE/EE allows remote attackers to read default branch names of projects with member-only repositories. The project details view renders the restricted branch name in page metadata, including repository_ref and autocomplete attributes, despite denying repository access. Exploitation requires a visible project with repository access limited to members; the disclosed information is only the default branch name.
Summary
What happened
Information disclosure in GitLab CE/EE allows remote attackers to read default branch names of projects with member-only repositories. The project details view renders the restricted branch name in page metadata, including repository_ref and autocomplete attributes, despite denying repository access. Exploitation requires a visible project with repository access limited to members; the disclosed information is only the default branch name.
The record
- CVE
- CVE-2021-39941
- Published
- Dec 13, 2021
- Updated
- Aug 4, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-200
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 13, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=>=12.0, <14.3.6
- Affected versionversion=>=14.4, <14.4.4
- Affected versionversion=>=14.5, <14.5.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
- Unauthenticated project-page metadata disclosure 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