# GHSA-48gc-5j93-5cfq: Path Traversal in serve

> Attackers can access hidden folders and files via relative paths in the serve static file server.

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

## What is GHSA-48gc-5j93-5cfq?

GHSA-48gc-5j93-5cfq is a path traversal vulnerability in serve, published on 11 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Versions of `serve` prior to 10.1.2 are vulnerable to Path Traversal. Explicitly ignored folders can be accessed through relative paths, which allows attackers to access hidden folders and files.

## Recommendation

Upgrade to version 10.1.2 or later.

## Which versions are affected by GHSA-48gc-5j93-5cfq?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `serve` | npm | All versions | 10.1.2 |
| `serve` | npm | All versions | 10.1.2 |

## How do I fix GHSA-48gc-5j93-5cfq?

Upgrade serve to 10.1.2 or later.

## Is GHSA-48gc-5j93-5cfq being exploited?

There is no known exploitation of GHSA-48gc-5j93-5cfq in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-48gc-5j93-5cfq and fix it if it is affected.

What it is: GHSA-48gc-5j93-5cfq is a path traversal vulnerability in serve, published on 11 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-48gc-5j93-5cfq in the wild and no public exploit code.

Affected packages and fixed versions:
- serve (npm): affected all versions; fixed in 10.1.2
- serve (npm): affected all versions; fixed in 10.1.2

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-48gc-5j93-5cfq/ (Markdown: https://insights.sbomify.com/GHSA-48gc-5j93-5cfq/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-48gc-5j93-5cfq

---
From sbomify Insights: https://insights.sbomify.com/GHSA-48gc-5j93-5cfq/
Summaries are generated and may contain mistakes; the official description above is the record.