# CVE-2019-5416: Path Traversal in localhost-now

> Attackers can read arbitrary files on the remote server via path traversal in the localhost-now 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:** No
- **Published:** 17 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-qwj8-p662-3m7x

## What is CVE-2019-5416?

CVE-2019-5416 is a high-severity path traversal vulnerability in localhost-now, published on 17 Mar 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 localhost-now npm package version 1.0.2 allows the attackers to read content of arbitrary files on the remote server.

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

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

2 open source packages ship an affected version, including localhost-now. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `localhost-now` | npm | All versions to 1.0.2 | None |
| `localhost-now` | npm | All versions to 1.0.2 | None |

Products: Localhost-Now Project Localhost-Now.

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

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

## Is CVE-2019-5416 being exploited?

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

## Other vulnerabilities in localhost-now

- [CVE-2018-3729](https://insights.sbomify.com/CVE-2018-3729/): Path Traversal in localhost-now (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-5416 is a high-severity path traversal vulnerability in localhost-now, published on 17 Mar 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-5416 in the wild and no public exploit code.

Affected packages and fixed versions:
- localhost-now (npm): affected all versions up to 1.0.2; no fix listed
- localhost-now (npm): affected all versions up to 1.0.2; 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-5416/ (Markdown: https://insights.sbomify.com/CVE-2019-5416/index.md)
```

## Sources

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

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