CVE-2023-3363

Insertion of Sensitive Information into Log File in GitLab

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`.

Remediation

Solution:

  • Upgrade to versions 15.11.10, 16.0.6, 16.1.1 or above.

Category

3.9
CVSS
Severity: Low
CVSS 3.1 •
EPSS 0.01%
Affected: GitLab GitLab
Published at:
Updated at:

References

Link Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/409034 issue tracking broken link

Frequently Asked Questions

What is the severity of CVE-2023-3363?
CVE-2023-3363 has been scored as a low severity vulnerability.
How to fix CVE-2023-3363?
To fix CVE-2023-3363: Upgrade to versions 15.11.10, 16.0.6, 16.1.1 or above.
Is CVE-2023-3363 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2023-3363 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2023-3363?
CVE-2023-3363 affects GitLab GitLab.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.