CVE-2023-3102

Public Exploit
Insertion of Sensitive Information Into Sent Data in GitLab

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.

Remediation

Solution:

  • Upgrade to versions 16.0.6, 16.1.1 or above.

Category

5.3
CVSS
Severity: Medium
CVSS 3.1 •
EPSS 0.21%
Affected: GitLab GitLab
Published at:
Updated at:

References

Link Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/414269 issue tracking broken link
https://hackerone.com/reports/2012073 broken link exploit permissions required technical description

Frequently Asked Questions

What is the severity of CVE-2023-3102?
CVE-2023-3102 has been scored as a medium severity vulnerability.
How to fix CVE-2023-3102?
To fix CVE-2023-3102: Upgrade to versions 16.0.6, 16.1.1 or above.
Is CVE-2023-3102 being actively exploited in the wild?
It is possible that CVE-2023-3102 is being exploited or will be exploited in a near future based on public information. 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-2023-3102?
CVE-2023-3102 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.