Skip to content
Fencer Intel
medium 5.3

CVE-2023-3102 json

Insertion of Sensitive Information Into Sent Data in GitLab

published 3y ago modified 4mo ago also BIT-gitlab-2023-3102 , EUVD-2023-43789

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 48%
public exploits
0
none known

Summary

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.

Patch / fix

  • bitnami gitlab 16.0.6, 16.1.1
  • GitLab GitLab 16.0.6, 16.1.1

Is CVE-2023-3102 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
2y ago

Exploit prediction

0.58% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-14).

Exploits and checks

  • hackerone.com https://hackerone.com/reports/2012073 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OSV 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
bitnami gitlab
>=16.0.0, <16.0.6
>=16.1.0, <16.1.1
16.0.6
16.1.1

Affected products

  • GitLab GitLab

Classification

Weakness
  • CWE-201 Insertion of Sensitive Information Into Sent Data
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Enhance with deb and rpm package type records.