# CVE-2022-4206: Information disclosure in DAST API scanner

> An attacker can view sensitive Authorization headers in vulnerability reports generated by the DAST API scanner, potentially exposing credentials.

- **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:** 1 Feb 2023
- **Updated:** 27 Mar 2025
- **Also known as:** GHSA-q474-j5v6-f4jg, UBUNTU-CVE-2022-4206

## What is CVE-2022-4206?

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

### Official description

A sensitive information leak issue has been discovered in all versions of DAST API scanner from 1.6.50 prior to 2.0.102, exposing the Authorization header in the vulnerability report

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2022-4206?

It affects 1 product.


Products: Gitlab Dast Api Scanner.

## How do I fix CVE-2022-4206?

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

## Is CVE-2022-4206 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-4206 and fix it if it is affected.

What it is: CVE-2022-4206 is a medium-severity vulnerability in GitLab DAST API scanner, published on 1 Feb 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-2022-4206 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-2022-4206/ (Markdown: https://insights.sbomify.com/CVE-2022-4206/index.md)
```

## Sources

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

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