CVE intelligence and bounded remediation
CVE-2023-4378 — Gitlab Gitlab security vulnerability
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.
- Severity
- Medium
- CVSS
- 5.5 (3.1)
- Published
- 2023-09-01
- CISA KEV
- Not currently listed
- Ecosystem
- software/application
- Weaknesses
- CWE-201
Affected products
- gitlab / gitlab
- gitlab / gitlab / 16.3.0
Matched remediation archetype
Information disclosure and sensitive data exposure
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Trace sensitive data through responses, errors, logs, metrics, traces, caches, exports, files, backups, and client bundles.
- Identify affected subjects, tenants, retention windows, access controls, and downstream copies without opening unnecessary sensitive records.
- Review metadata, timing, status, length, and existence signals as well as direct content disclosure.
Remediate safely
- Minimize collection and output, apply field-level authorization and redaction at a centralized boundary, and return generic external errors.
- Remove secrets and sensitive data from logs, artifacts, URLs, caches, and client-side bundles; rotate credentials that may have been exposed.
- Update the affected component and add synthetic-data tests for response, error, observability, and export paths.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.