CVE-2023-3363: Insertion of Sensitive Information into Log File in GitLab
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 15.11.10 - Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 16.0.6 - Upgrade
Upgrade
GitLab CE/EEto a version that resolves this vulnerability.Fixed in 16.1.1
Event History
Frequently Asked Questions
What is the vulnerability ID of this information disclosure issue in Gitlab CE/EE?
The vulnerability ID is CVE-2023-3363.
Which versions of Gitlab CE/EE are affected by this vulnerability?
All versions from 13.6 prior to 15.11.10, all versions from 16.0 prior to 16.0.6, and all versions from 16.1 prior to 16.1.1 are affected.
What is the severity of CVE-2023-3363?
The severity of CVE-2023-3363 is low.
What is the impact of this vulnerability?
The vulnerability results in the Sidekiq log including webhook tokens when the log format is set to `default`, leading to information disclosure.
Is there a fix for CVE-2023-3363?
Yes, upgrading Gitlab CE/EE to version 15.11.10, 16.0.6, or 16.1.1 (or later) will fix the vulnerability.