# CVE-2019-5447: Path Traversal in http-file-server

> Attackers can list files in arbitrary folders due to a path traversal flaw in the http-file-server npm module.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2mp5-m968-gwr2

## What is CVE-2019-5447?

CVE-2019-5447 is a medium-severity path traversal vulnerability in http-file-server, published on 15 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A path traversal vulnerability in <= v0.2.6 of http-file-server npm module allows attackers to list files in arbitrary folders.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2019-5447?

2 open source packages ship an affected version, including http-file-server. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `http-file-server` | npm | All versions | None |
| `http-file-server` | npm | All versions | None |

Products: Http-File-Server Project Http-File-Server.

## How do I fix CVE-2019-5447?

No fix has been published for CVE-2019-5447 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-5447 being exploited?

There is no known exploitation of CVE-2019-5447 in the wild and no public exploit code.

## Other vulnerabilities in http-file-server

- [CVE-2019-5458](https://insights.sbomify.com/CVE-2019-5458/): Cross-Site Scripting in http-file-server (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-5447 and fix it if it is affected.

What it is: CVE-2019-5447 is a medium-severity path traversal vulnerability in http-file-server, published on 15 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 CVE-2019-5447 in the wild and no public exploit code.

Affected packages and fixed versions:
- http-file-server (npm): affected all versions; no fix listed
- http-file-server (npm): affected all versions; 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/CVE-2019-5447/ (Markdown: https://insights.sbomify.com/CVE-2019-5447/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-5447
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-5447
- OSV: https://osv.dev/vulnerability/CVE-2019-5447

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-5447/
Summaries are generated and may contain mistakes; the official description above is the record.