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

- **Severity:** Low 3.9 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jul 2023
- **Updated:** 5 Nov 2024
- **Also known as:** BIT-gitlab-2023-3363, GHSA-2wh2-fff9-4m63, UBUNTU-CVE-2023-3363

## 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 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2023-3363?

1 open source package ship an affected version, including gitlab. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gitlab` | Bitnami | From 13.6.0 | 15.11.10, 16.0.6, 16.1.1 |

Products: 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](https://insights.sbomify.com/CVE-2026-97229/): GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound (critical 10.0, exploited in the wild)
- [CVE-2026-85706](https://insights.sbomify.com/CVE-2026-85706/): GitLab Community Edition and Enterprise Edition Path Traversal (critical 10.0, exploited in the wild)
- [CVE-2023-7028](https://insights.sbomify.com/CVE-2023-7028/): GitLab Community and Enterprise Editions Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2021-22205](https://insights.sbomify.com/CVE-2021-22205/): GitLab Community and Enterprise Editions Remote Code Execution (critical 10.0, exploited in the wild)
- [CVE-2021-39935](https://insights.sbomify.com/CVE-2021-39935/): GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF) (medium 6.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-3363 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-3363 exists.

Affected packages and fixed versions:
- gitlab (Bitnami): affected from 13.6.0; fixed in 15.11.10, 16.0.6, 16.1.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-3363/ (Markdown: https://insights.sbomify.com/CVE-2023-3363/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-3363
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-3363
- OSV: https://osv.dev/vulnerability/CVE-2023-3363

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-3363/
Summaries are generated and may contain mistakes; the official description above is the record.