# GHSA-73cw-jxmm-qpgh: Path Traversal in localhost-now

> Attackers can read arbitrary files from the server via path traversal in the localhost-now library, requiring immediate removal of the module.

- **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:** 11 Jun 2019

## What is GHSA-73cw-jxmm-qpgh?

GHSA-73cw-jxmm-qpgh is a path traversal vulnerability in localhost-now, published on 11 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions of `localhost-now` are vulnerable to path traversal. This vulnerability is a bypass to the path traversal fix introduced in version 1.0.2

Proof of concept:

```
$ curl -v --path-as-is "http://IP:5432/..././..././..././..././..././..././..././..././..././..././etc/passwd" 
```

## Recommendation

No fix is currently available for this vulnerability. It is our recommendation to not install or use this module until a fix is available.

## Which versions are affected by GHSA-73cw-jxmm-qpgh?

2 open source packages ship an affected version, including localhost-now.


| 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 |

## How do I fix GHSA-73cw-jxmm-qpgh?

No fix has been published for GHSA-73cw-jxmm-qpgh yet. Limit exposure of the affected software until one is available.

## Is GHSA-73cw-jxmm-qpgh being exploited?

There is no known exploitation of GHSA-73cw-jxmm-qpgh in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-73cw-jxmm-qpgh and fix it if it is affected.

What it is: GHSA-73cw-jxmm-qpgh is a path traversal vulnerability in localhost-now, published on 11 Jun 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-73cw-jxmm-qpgh 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/GHSA-73cw-jxmm-qpgh/ (Markdown: https://insights.sbomify.com/GHSA-73cw-jxmm-qpgh/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-73cw-jxmm-qpgh

---
From sbomify Insights: https://insights.sbomify.com/GHSA-73cw-jxmm-qpgh/
Summaries are generated and may contain mistakes; the official description above is the record.