# CVE-2022-35406: Open redirect in n/a

> Attackers can disclose URLs by crafting responses that Burp Suite incorrectly interprets as redirects in Repeater or Intruder.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-3x46-hg82-953f

## What is CVE-2022-35406?

CVE-2022-35406 is a medium-severity vulnerability in n/a, published on 8 Jul 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A URL disclosure issue was discovered in Burp Suite before 2022.6. If a user views a crafted response in the Repeater or Intruder, it may be incorrectly interpreted as a redirect.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

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

It affects 1 product.


Products: Portswigger Burp Suite.

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

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

## Is CVE-2022-35406 being exploited?

There is no known exploitation of CVE-2022-35406 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2018-1153](https://insights.sbomify.com/CVE-2018-1153/): Security feature bypass in Burp Suite Community Edition (high 7.4)
- [CVE-2021-44230](https://insights.sbomify.com/CVE-2021-44230/): Misconfiguration in n/a (medium 6.5)
- [CVE-2021-29416](https://insights.sbomify.com/CVE-2021-29416/): Server-side request forgery in n/a (medium 6.5)
- [CVE-2018-10377](https://insights.sbomify.com/CVE-2018-10377/): Weak cryptography in n/a (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-35406 is a medium-severity vulnerability in n/a, published on 8 Jul 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-35406 in the wild and no public exploit code.

Affected product: n/a. 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-35406/ (Markdown: https://insights.sbomify.com/CVE-2022-35406/index.md)
```

## Sources

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

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