CVE-2023-3102 Insertion of Sensitive Information Into Sent Data in GitLab
Attackers can access titles of private issues and merge requests in GitLab EE, exposing sensitive project information.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2023-3102?
CVE-2023-3102 is a medium-severity vulnerability in Gitlab Gitlab, published on 21 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
A sensitive information leak issue has been discovered in GitLab EE affecting all versions starting from 16.0 before 16.0.6, all versions starting from 16.1 before 16.1.1, which allows access to titles of private issue and MR.
Weakness: CWE-201
Which versions are affected by CVE-2023-3102?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 16.0.0 | 16.0.6, 16.1.1 |
Products include Gitlab Gitlab.
How do I fix CVE-2023-3102?
Upgrade gitlab to a fixed version for your release line: 16.0.6 or 16.1.1.
Is CVE-2023-3102 being exploited?
There is no known exploitation of CVE-2023-3102 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-2023-3102, GHSA-5h2f-9v3w-h48r.