# CVE-2023-0326: Information disclosure in GitLab DAST API scanner

> Attackers can view leaked Authorization headers in vulnerability reports, exposing sensitive credentials to anyone with report access.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Mar 2023
- **Updated:** 19 Feb 2025
- **Also known as:** CVE-2023-1648, GHSA-5885-hj3c-73cr

## What is CVE-2023-0326?

CVE-2023-0326 is a medium-severity vulnerability in GitLab DAST API scanner, published on 27 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue has been discovered in GitLab DAST API scanner affecting all versions starting from 1.6.50 before 2.11.0, where Authorization headers was leaked in vulnerability report evidence.

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

It affects 1 product.


Products: Gitlab Dynamic Application Security Testing Analyzer.

## How do I fix CVE-2023-0326?

No fix has been published for CVE-2023-0326 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-0326 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-0326 exists.

## Other vulnerabilities in GitLab DAST API scanner

- [CVE-2022-3767](https://insights.sbomify.com/CVE-2022-3767/): Server-side request forgery in DAST (high 7.7)
- [CVE-2022-4317](https://insights.sbomify.com/CVE-2022-4317/): Open redirect in DAST (medium 5.0)
- [CVE-2022-4315](https://insights.sbomify.com/CVE-2022-4315/): Missing authorization in GitLab (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-0326 is a medium-severity vulnerability in GitLab DAST API scanner, published on 27 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-0326 exists.

Affected product: GitLab DAST API scanner. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-0326/ (Markdown: https://insights.sbomify.com/CVE-2023-0326/index.md)
```

## Sources

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

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