CVE-2022-3375
First published: Wed Apr 05 2023(Updated: )
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.
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=11.10.0<15.8.5 | |
| GitLab | >=11.10.0<15.8.5 | |
| GitLab | >=15.9.0<15.9.4 | |
| GitLab | >=15.9.0<15.9.4 | |
| GitLab | =15.10.0 | |
| GitLab | =15.10.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2022-3375?
CVE-2022-3375 has been classified as a medium severity vulnerability.
How do I fix CVE-2022-3375?
To fix CVE-2022-3375, update GitLab to version 15.8.5, 15.9.4, or 15.10.1 or later.
What is the impact of CVE-2022-3375?
The impact of CVE-2022-3375 allows attackers with a fork of a project to disclose branch names.
Which versions of GitLab are affected by CVE-2022-3375?
CVE-2022-3375 affects GitLab versions from 11.10 up to but not including 15.8.5, from 15.9 up to but not including 15.9.4, and 15.10.0.
Is this vulnerability exploitable remotely in CVE-2022-3375?
Yes, CVE-2022-3375 can be exploited remotely by an attacker who has access to a fork of the affected project.
- agent/type
- agent/references
- agent/author
- agent/description
- agent/severity
- agent/event
- agent/first-publish-date
- collector/nvd-index
- agent/software-canonical-lookup-request
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/weakness
- agent/source
- agent/last-modified-date
- agent/tags
- vendor/gitlab
- canonical/gitlab
- version/gitlab/11.10.0
- version/gitlab/15.9.0
- version/gitlab/15.10.0