CVE-2022-3375 Information disclosure in GitLab
Attackers with a fork of a private project can disclose branch names, exposing sensitive repository structure information.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2022-3375?
CVE-2022-3375 is a low-severity vulnerability in Gitlab Gitlab, published on 5 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
An issue has been discovered in GitLab affecting all versions starting from 11.10 before 15.8.5, all versions starting from 15.9 before 15.9.4, all versions starting from 15.10 before 15.10.1. It was possible to disclose the branch names when attacker has a fork of a project that was switched to private.
Weakness: CWE-535
Which versions are affected by CVE-2022-3375?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 11.10.0 | 15.8.5, 15.9.4, 15.10.1 |
Products include Gitlab Gitlab.
How do I fix CVE-2022-3375?
Upgrade gitlab to a fixed version for your release line: 15.8.5, 15.9.4 or 15.10.1.
Is CVE-2022-3375 being exploited?
There is no known exploitation of CVE-2022-3375 in the wild and no public exploit code.
Other vulnerabilities in Gitlab Gitlab
- CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound
- CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)
Sources
Also known as BIT-gitlab-2022-3375, GHSA-c3qm-r5gp-mgpm, UBUNTU-CVE-2022-3375.