# GHSA-6qh5-wx38-q92g: Directory Traversal in ltt.js

> Attackers can read arbitrary files on the server via directory traversal in ltt.js; users should avoid using this package in production.

- **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:** 30 May 2019

## What is GHSA-6qh5-wx38-q92g?

GHSA-6qh5-wx38-q92g is a path traversal vulnerability in ltt.js, published on 30 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Affected versions of `ltt.js` resolve relative file paths, resulting in a directory traversal vulnerability. A malicious actor can use this vulnerability to access files outside of the intended directory root, which may result in the disclosure of private files on the vulnerable system.

Example request:
```
GET /../../../../../../../../../../etc/passwd HTTP/1.1
host:foo
```

## Recommendation

No patch is available for this vulnerability.

It is recommended that the package is only used for local development, and if the functionality is needed for production, a different package is used instead.

## Which versions are affected by GHSA-6qh5-wx38-q92g?

2 open source packages ship an affected version, including ltt.js.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ltt.js` | npm | All versions | None |
| `ltt.js` | npm | All versions | None |

## How do I fix GHSA-6qh5-wx38-q92g?

No fix has been published for GHSA-6qh5-wx38-q92g yet. Limit exposure of the affected software until one is available.

## Is GHSA-6qh5-wx38-q92g being exploited?

There is no known exploitation of GHSA-6qh5-wx38-q92g in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-6qh5-wx38-q92g and fix it if it is affected.

What it is: GHSA-6qh5-wx38-q92g is a path traversal vulnerability in ltt.js, published on 30 May 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-6qh5-wx38-q92g in the wild and no public exploit code.

Affected packages and fixed versions:
- ltt.js (npm): affected all versions; no fix listed
- ltt.js (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/GHSA-6qh5-wx38-q92g/ (Markdown: https://insights.sbomify.com/GHSA-6qh5-wx38-q92g/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-6qh5-wx38-q92g

---
From sbomify Insights: https://insights.sbomify.com/GHSA-6qh5-wx38-q92g/
Summaries are generated and may contain mistakes; the official description above is the record.