CVE-2023-1936 Exposure of Private Personal Information to an Unauthorized Actor in GitLab
An attacker can leak the email address of a user who created a service desk issue in GitLab.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2023-1936?
CVE-2023-1936 is a low-severity vulnerability in Gitlab Gitlab, published on 11 Jul 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.7 before 15.11.10, all versions starting from 16.0 before 16.0.6, all versions starting from 16.1 before 16.1.1, which allows an attacker to leak the email address of a user who created a service desk issue.
Weakness: CWE-359
Which versions are affected by CVE-2023-1936?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 13.7.0 | 15.11.10, 16.0.6, 16.1.1 |
Products include Gitlab Gitlab.
How do I fix CVE-2023-1936?
Upgrade gitlab to a fixed version for your release line: 15.11.10, 16.0.6 or 16.1.1.
Is CVE-2023-1936 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-1936 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-2023-1936, GHSA-x8x7-j36c-mp3c, UBUNTU-CVE-2023-1936.