# GHSA-4x7w-frcq-v4m3: Path Traversal in @wturyn/swagger-injector

> Attackers can read server files outside the configured directory due to unsanitized URLs in the swagger-injector npm package.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Sep 2020

## What is GHSA-4x7w-frcq-v4m3?

GHSA-4x7w-frcq-v4m3 is a path traversal vulnerability in @wturyn/swagger-injector, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions of `@wturyn/swagger-injector` are vulnerable to Path Traversal. The package fails to sanitize URLs, allowing attackers to access server files outside of the configured `dist` folder using relative paths.

## Recommendation

No fix is currently available. Consider using an alternative package until a fix is made available.

## Which versions are affected by GHSA-4x7w-frcq-v4m3?

2 open source packages ship an affected version, including @wturyn/swagger-injector.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@wturyn/swagger-injector` | npm | From 0.0.0 | None |
| `@wturyn/swagger-injector` | npm | From 0.0.0 | None |

## How do I fix GHSA-4x7w-frcq-v4m3?

No fix has been published for GHSA-4x7w-frcq-v4m3 yet. Limit exposure of the affected software until one is available.

## Is GHSA-4x7w-frcq-v4m3 being exploited?

There is no known exploitation of GHSA-4x7w-frcq-v4m3 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-4x7w-frcq-v4m3 and fix it if it is affected.

What it is: GHSA-4x7w-frcq-v4m3 is a path traversal vulnerability in @wturyn/swagger-injector, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-4x7w-frcq-v4m3 in the wild and no public exploit code.

Affected packages and fixed versions:
- @wturyn/swagger-injector (npm): affected from 0.0.0; no fix listed
- @wturyn/swagger-injector (npm): affected from 0.0.0; no fix listed

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-4x7w-frcq-v4m3/ (Markdown: https://insights.sbomify.com/GHSA-4x7w-frcq-v4m3/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-4x7w-frcq-v4m3

---
From sbomify Insights: https://insights.sbomify.com/GHSA-4x7w-frcq-v4m3/
Summaries are generated and may contain mistakes; the official description above is the record.