CVE-2023-3993 Insertion of Sensitive Information into Log File in GitLab
Attackers with log access can retrieve sensitive access tokens from GitLab logs, potentially leading to unauthorized account access.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2023-3993?
CVE-2023-3993 is a medium-severity vulnerability in Gitlab Gitlab, published on 2 Aug 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Official description
An issue has been discovered in GitLab EE affecting all versions starting from 14.3 before 16.0.8, all versions starting from 16.1 before 16.1.3, all versions starting from 16.2 before 16.2.2. Access tokens may have been logged when a query was made to a specific endpoint.
Weakness: CWE-532
Which versions are affected by CVE-2023-3993?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 14.3.0 | 16.0.8, 16.1.3, 16.2.2 |
Products include Gitlab Gitlab.
How do I fix CVE-2023-3993?
Upgrade gitlab to a fixed version for your release line: 16.0.8, 16.1.3 or 16.2.2.
Is CVE-2023-3993 being exploited?
There is no known exploitation of CVE-2023-3993 in the wild and no public exploit code.
Other vulnerabilities in Gitlab Gitlab
- CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound
- CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)
Sources
Also known as BIT-gitlab-2023-3993, GHSA-cjf2-62xp-p6mj.