CVE-2022-3375

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.

Category

3.1
CVSS
Severity: Low
CVSS 3.1 •
EPSS 0.43%
Vendor Advisory gitlab.com
Affected: GitLab GitLab
Published at:
Updated at:

References

Link Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/376041 broken link
https://hackerone.com/reports/1710533 permissions required
https://gitlab.com/gitlab-org/cves/-/blob/master/2022/CVE-2022-3375.json vendor advisory

Frequently Asked Questions

What is the severity of CVE-2022-3375?
CVE-2022-3375 has been scored as a low severity vulnerability.
How to fix CVE-2022-3375?
To fix CVE-2022-3375, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2022-3375 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2022-3375 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2022-3375?
CVE-2022-3375 affects GitLab GitLab.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.