Vulnerability · Published Sep 1, 2023 · Assigned by GitLab

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

Medium 5.5

In plain English

A medium-severity security flaw in GitLab from GitLab. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.5% (higher than 44% of all known vulnerabilities).

Severity (CVSS 3.1)5.5Medium

Exploit odds (30 days)0.5%top 56.3% of all CVEs

Exploited in the wildNo reportsCISA SSVC: poc

Attack toolingNoneno public tooling known

Official description

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.

Affected products (as reported)

Vendor	Product	Versions
GitLab	GitLab	11.8 – before 16.1.516.2 – before 16.2.516.3 – before 16.3.1

Weakness: CWE-201 · Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N

References

GitLab Issue #422134 issue-tracking, permissions-required
HackerOne Bug Bounty Report #2104591 technical-description, exploit