What is CVE-2023-3102?

CVE-2023-3102 is a vulnerability in GitLab EE that allows access to titles of private issues and MR (Merge Requests).

What is the severity of CVE-2023-3102?

The severity of CVE-2023-3102 is medium, with a CVSS score of 5.3.

Which versions of GitLab EE are affected by CVE-2023-3102?

All versions starting from 16.0 before 16.0.6 and all versions starting from 16.1 before 16.1.1 of GitLab EE are affected by CVE-2023-3102.

How can the sensitive information leak issue be mitigated in GitLab EE?

To mitigate the sensitive information leak issue in GitLab EE, it is recommended to update to version 16.0.6 or higher for versions starting from 16.0 before 16.0.6, and to version 16.1.1 or higher for versions starting from 16.1 before 16.1.1.

Where can I find more information about CVE-2023-3102?

More information about CVE-2023-3102 can be found at the following references: [HackerOne report](https://hackerone.com/reports/2012073) and [GitLab issue](https://gitlab.com/gitlab-org/gitlab/-/issues/414269).

Vulnerability/
CVE-2023-3102

medium

5.3

CWE

200 201

21/7/2023

3/10/2024

CVE-2023-3102: Insertion of Sensitive Information Into Sent Data in GitLab

First published: Fri Jul 21 2023(Updated: )

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.

Credit: cve@gitlab.com cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab GitLab	>=16.0.0<16.0.6
GitLab GitLab	=16.1.0

Remedy

Upgrade to versions 16.0.6, 16.1.1 or above.

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is CVE-2023-3102?
CVE-2023-3102 is a vulnerability in GitLab EE that allows access to titles of private issues and MR (Merge Requests).
What is the severity of CVE-2023-3102?
The severity of CVE-2023-3102 is medium, with a CVSS score of 5.3.
Which versions of GitLab EE are affected by CVE-2023-3102?
All versions starting from 16.0 before 16.0.6 and all versions starting from 16.1 before 16.1.1 of GitLab EE are affected by CVE-2023-3102.
How can the sensitive information leak issue be mitigated in GitLab EE?
To mitigate the sensitive information leak issue in GitLab EE, it is recommended to update to version 16.0.6 or higher for versions starting from 16.0 before 16.0.6, and to version 16.1.1 or higher for versions starting from 16.1 before 16.1.1.
Where can I find more information about CVE-2023-3102?
More information about CVE-2023-3102 can be found at the following references: [HackerOne report](https://hackerone.com/reports/2012073) and [GitLab issue](https://gitlab.com/gitlab-org/gitlab/-/issues/414269).

collector/nvd-latest
agent/references
agent/author
agent/type
agent/description
collector/nvd-index
agent/software-canonical-lookup-request
agent/softwarecombine
agent/severity
agent/remedy
agent/first-publish-date
agent/event
agent/tags
collector/mitre-cve
source/MITRE
agent/weakness
agent/last-modified-date
agent/title
collector/nvd-api
source/NVD
agent/software-canonical-lookup
vendor/gitlab
canonical/gitlab gitlab
version/gitlab gitlab/16.0.0
version/gitlab gitlab/16.1.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.