Insertion of Sensitive Information Into Sent Data in GitLab

published 2023-09-01 3 y ago modified 2026-09-10 1 mo ago also BIT-gitlab-2023-4378 , EUVD-2023-54242

cvss: 5.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 43%
public exploits: 0; none known

An issue has been discovered in GitLab CE/EE affecting all versions starting from 11.8 before 16.1.5, all versions starting from 16.2 before 16.2.5, all versions starting from 16.3 before 16.3.1. A malicious Maintainer can, under specific circumstances, leak the sentry token by changing the configured URL in the Sentry error tracking settings page. This was as a result of an incomplete fix for CVE-2022-4365.

Patch / fix

fixed in 2

bitnami gitlab 16.1.5, 16.2.5, 16.3.1
GitLab GitLab 16.1.5, 16.2.5, 16.3.1

CISA SSVC

Exploitation: Proof of concept is public
Automatable: no
Technical impact: partial
Assessed: 2 y ago (2024-08-30)

Exploit prediction

0.51% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

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

CVSS scores

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

Affected packages

ecosystem	package	affected	fixed in
bitnami	gitlab	>=11.8.0, <16.1.5 >=16.2.0, <16.2.5 >=16.3.0, <16.3.1	16.1.5 16.2.5 16.3.1

Affected products

GitLab GitLab

Classification

Weakness

CWE-201 Insertion of Sensitive Information Into Sent Data

Technology feeds

GitLab rss critical rss

References

hackerone.com /reports/2104591
technical-description, exploit, permissions-required, web
gitlab.com /gitlab-org/gitlab/-/issues/422134
issue-tracking, permissions-required, broken-link, web
nvd.nist.gov /vuln/detail/CVE-2023-4378
web

Sources

Fencer Vulns 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.

Summary