# GHSA-g8m7-qhv7-9h5x: Path Traversal in serve-here.js

> Attackers can read arbitrary server files outside the served directory due to unsanitized URL handling in serve-here.js.

- **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:** 5 Jul 2019

## What is GHSA-g8m7-qhv7-9h5x?

GHSA-g8m7-qhv7-9h5x is a path traversal vulnerability in serve-here, published on 5 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Versions of `serve-here.js` prior to 1.2.0 are vulnerable to Path Traversal. The package fails to sanitize URLs, allowing attackers to access server files outside of the served folder using relative paths.

## Recommendation

Upgrade to version 1.2.0 or later.

## Which versions are affected by GHSA-g8m7-qhv7-9h5x?

2 open source packages ship an affected version, including serve-here.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `serve-here` | npm | All versions to 3.2.0 | None |
| `serve-here` | npm | All versions to 3.2.0 | None |

## How do I fix GHSA-g8m7-qhv7-9h5x?

No fix has been published for GHSA-g8m7-qhv7-9h5x yet. Limit exposure of the affected software until one is available.

## Is GHSA-g8m7-qhv7-9h5x being exploited?

There is no known exploitation of GHSA-g8m7-qhv7-9h5x in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-g8m7-qhv7-9h5x and fix it if it is affected.

What it is: GHSA-g8m7-qhv7-9h5x is a path traversal vulnerability in serve-here, published on 5 Jul 2019. 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-g8m7-qhv7-9h5x in the wild and no public exploit code.

Affected packages and fixed versions:
- serve-here (npm): affected all versions up to 3.2.0; no fix listed
- serve-here (npm): affected all versions up to 3.2.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-g8m7-qhv7-9h5x/ (Markdown: https://insights.sbomify.com/GHSA-g8m7-qhv7-9h5x/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-g8m7-qhv7-9h5x

---
From sbomify Insights: https://insights.sbomify.com/GHSA-g8m7-qhv7-9h5x/
Summaries are generated and may contain mistakes; the official description above is the record.