# GHSA-x9p2-fxq6-2m5f: Reverse Tabnapping in swagger-ui

> Attackers can exploit reverse tabnapping in Swagger UI to access the original page's window object, facilitating phishing attacks against users.

- **Severity:** Not scored
- **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:** Yes
- **Published:** 20 Jun 2019

## What is GHSA-x9p2-fxq6-2m5f?

GHSA-x9p2-fxq6-2m5f is a vulnerability in swagger-ui, published on 20 Jun 2019. 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

Versions of `swagger-ui` prior to 3.18.0 are vulnerable to [Reverse Tabnapping](https://www.owasp.org/index.php/Reverse_Tabnabbing). The package uses `target='_blank'` in anchor tags, allowing attackers to access `window.opener` for the original page. This is commonly used for phishing attacks.

## Recommendation

Upgrade to version 3.18.0 or later.

## Which versions are affected by GHSA-x9p2-fxq6-2m5f?

2 open source packages ship an affected version, including swagger-ui.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `swagger-ui` | npm | All versions | 3.18.0 |
| `swagger-ui` | npm | All versions | 3.18.0 |

## How do I fix GHSA-x9p2-fxq6-2m5f?

Upgrade swagger-ui to 3.18.0 or later.

## Is GHSA-x9p2-fxq6-2m5f being exploited?

There is no known exploitation of GHSA-x9p2-fxq6-2m5f in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-x9p2-fxq6-2m5f and fix it if it is affected.

What it is: GHSA-x9p2-fxq6-2m5f is a vulnerability in swagger-ui, published on 20 Jun 2019. 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 GHSA-x9p2-fxq6-2m5f in the wild and no public exploit code.

Affected packages and fixed versions:
- swagger-ui (npm): affected all versions; fixed in 3.18.0
- swagger-ui (npm): affected all versions; fixed in 3.18.0

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/GHSA-x9p2-fxq6-2m5f/ (Markdown: https://insights.sbomify.com/GHSA-x9p2-fxq6-2m5f/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-x9p2-fxq6-2m5f

---
From sbomify Insights: https://insights.sbomify.com/GHSA-x9p2-fxq6-2m5f/
Summaries are generated and may contain mistakes; the official description above is the record.