# CVE-2018-16479: Path Traversal in http-live-simulator

> An attacker can read arbitrary files on the server by exploiting a path traversal flaw in the http-live-simulator npm package.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** Yes
- **Published:** 1 Feb 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7c9w-qmrq-ff8r

## What is CVE-2018-16479?

CVE-2018-16479 is a high-severity path traversal vulnerability in HackerOne http-live-simulator, published on 1 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Path traversal vulnerability in http-live-simulator <1.0.7 causes unauthorized access to arbitrary files on disk by appending extra slashes after the URL.

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

## Which versions are affected by CVE-2018-16479?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `http-live-simulator` | npm | All versions | 1.0.7 |
| `http-live-simulator` | npm | All versions | 1.0.7 |

Products: Http-Live-Simulator Project Http-Live-Simulator.

## How do I fix CVE-2018-16479?

Upgrade http-live-simulator to 1.0.7 or later.

## Is CVE-2018-16479 being exploited?

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

## Other vulnerabilities in HackerOne http-live-simulator

- [CVE-2019-5423](https://insights.sbomify.com/CVE-2019-5423/): Path Traversal in http-live-simulator (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-16479 and fix it if it is affected.

What it is: CVE-2018-16479 is a high-severity path traversal vulnerability in HackerOne http-live-simulator, published on 1 Feb 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-2018-16479 in the wild and no public exploit code.

Affected packages and fixed versions:
- http-live-simulator (npm): affected all versions; fixed in 1.0.7
- http-live-simulator (npm): affected all versions; fixed in 1.0.7

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-2018-16479/ (Markdown: https://insights.sbomify.com/CVE-2018-16479/index.md)
```

## Sources

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

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