CVE-2023-3102

CVE-2023-3102 is a medium-severity vulnerability in Gitlab with a CVSS 3.x base score of 5.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-201.

Key facts

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.

Frequently asked questions

What is CVE-2023-3102?
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.
How severe is CVE-2023-3102?
CVE-2023-3102 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2023-3102 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (44th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2023-3102?
CVE-2023-3102 primarily affects Gitlab. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2023-3102?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2023-3102 published?
CVE-2023-3102 was published on 2023-07-21 and last updated on 2026-06-17.

References

Affected products (2)

More vulnerabilities in Gitlab

All CVEs affecting Gitlab →

Other CWE-201 vulnerabilities

Browse all CWE-201 vulnerabilities →