Private branch-name disclosure via push-option oracle
Published Apr 5, 2023 · Updated Feb 10, 2025
Information disclosure in GitLab allows remote authenticated users with an existing fork to enumerate branch names after a project becomes private. The merge-request push-options handler tests attacker-supplied target names against the private parent repository before checking repository access. Different push results reveal whether each guessed branch exists; exploitation requires push access to the retained fork and no user interaction.
Summary
What happened
Information disclosure in GitLab allows remote authenticated users with an existing fork to enumerate branch names after a project becomes private. The merge-request push-options handler tests attacker-supplied target names against the private parent repository before checking repository access. Different push results reveal whether each guessed branch exists; exploitation requires push access to the retained fork and no user interaction.
The record
- CVE
- CVE-2022-3375
- Published
- Apr 5, 2023
- Updated
- Feb 10, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-535, T1213.003
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 5, 2023CVE publishedPublication date reported by the CVE source.
- Feb 10, 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=>=11.10, <15.8.5
- Affected versionversion=>=15.10, <15.10.1
- Affected versionversion=>=15.9, <15.9.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
- GitLab private-branch enumeration 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