CVE-2023-3363 Insertion of Sensitive Information into Log File in GitLab
Attackers can read webhook tokens from Sidekiq logs if the log format is set to default, potentially compromising webhook security.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2023-3363?
CVE-2023-3363 is a low-severity vulnerability in Gitlab Gitlab, published on 13 Jul 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
An information disclosure issue in Gitlab CE/EE affecting all versions from 13.6 prior to 15.11.10, all versions from 16.0 prior to 16.0.6, all versions from 16.1 prior to 16.1.1, resulted in the Sidekiq log including webhook tokens when the log format was set to `default`.
Weakness: CWE-532
Which versions are affected by CVE-2023-3363?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 13.6.0 | 15.11.10, 16.0.6, 16.1.1 |
Products include Gitlab Gitlab.
How do I fix CVE-2023-3363?
Upgrade gitlab to a fixed version for your release line: 15.11.10, 16.0.6 or 16.1.1.
Is CVE-2023-3363 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-3363 exists.
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-3363, GHSA-2wh2-fff9-4m63, UBUNTU-CVE-2023-3363.