# GHSA-qjfh-xc44-rm9x: Path Traversal in file-static-server

> Attackers can read arbitrary server files via path traversal in the file-static-server npm package due to insufficient input sanitization.

- **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-qjfh-xc44-rm9x?

GHSA-qjfh-xc44-rm9x is a path traversal vulnerability in file-static-server, 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 `file-static-server` are vulnerable to Path Traversal.  Due to insufficient input sanitization in URLs, attackers can access server files by using relative paths when fetching files. 

## Recommendation

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

## Which versions are affected by GHSA-qjfh-xc44-rm9x?

2 open source packages ship an affected version, including file-static-server.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `file-static-server` | npm | From 0.0.0 | None |
| `file-static-server` | npm | From 0.0.0 | None |

## How do I fix GHSA-qjfh-xc44-rm9x?

No fix has been published for GHSA-qjfh-xc44-rm9x yet. Limit exposure of the affected software until one is available.

## Is GHSA-qjfh-xc44-rm9x being exploited?

There is no known exploitation of GHSA-qjfh-xc44-rm9x in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-qjfh-xc44-rm9x and fix it if it is affected.

What it is: GHSA-qjfh-xc44-rm9x is a path traversal vulnerability in file-static-server, 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-qjfh-xc44-rm9x in the wild and no public exploit code.

Affected packages and fixed versions:
- file-static-server (npm): affected from 0.0.0; no fix listed
- file-static-server (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-qjfh-xc44-rm9x/ (Markdown: https://insights.sbomify.com/GHSA-qjfh-xc44-rm9x/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-qjfh-xc44-rm9x

---
From sbomify Insights: https://insights.sbomify.com/GHSA-qjfh-xc44-rm9x/
Summaries are generated and may contain mistakes; the official description above is the record.