CVE-2022-4376 Information disclosure in GitLab
An attacker can map a private email address to a GitLab user account, exposing sensitive user 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-4376?
CVE-2022-4376 is a low-severity vulnerability in Gitlab Gitlab, published on 3 May 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 before 15.9.6, all versions starting from 15.10 before 15.10.5, all versions starting from 15.11 before 15.11.1. Under certain conditions, an attacker may be able to map a private email of a GitLab user to their GitLab account on an instance.
Which versions are affected by CVE-2022-4376?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 15.2.0 | 15.9.6, 15.10.5, 15.11.1 |
Products include Gitlab Gitlab.
How do I fix CVE-2022-4376?
Upgrade gitlab to a fixed version for your release line: 15.9.6, 15.10.5 or 15.11.1.
Is CVE-2022-4376 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4376 exists.
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-4376, GHSA-f3wg-5hg2-8j39, UBUNTU-CVE-2022-4376.