# CVE-2022-25895: Directory Traversal

> Attackers can read arbitrary files via directory traversal in lite-dev-server due to missing input sanitization on request URLs.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Dec 2022
- **Updated:** 16 Apr 2025
- **Also known as:** GHSA-pppv-ch8p-rp2w

## What is CVE-2022-25895?

CVE-2022-25895 is a high-severity path traversal vulnerability in lite-dev-server, published on 21 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions of package lite-dev-server are vulnerable to Directory Traversal due to missing input sanitization and sandboxes being employed to the req.url user input that is passed to the server code.

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

## Which versions are affected by CVE-2022-25895?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `lite-dev-server` | npm | All versions to 3.2.7 | None |
| `lite-dev-server` | npm | All versions to 3.2.7 | None |

Products: Lite-Dev-Server Project Lite-Dev-Server.

## How do I fix CVE-2022-25895?

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

## Is CVE-2022-25895 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-25895 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-25895 and fix it if it is affected.

What it is: CVE-2022-25895 is a high-severity path traversal vulnerability in lite-dev-server, published on 21 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-25895 exists.

Affected packages and fixed versions:
- lite-dev-server (npm): affected all versions up to 3.2.7; no fix listed
- lite-dev-server (npm): affected all versions up to 3.2.7; 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-2022-25895/ (Markdown: https://insights.sbomify.com/CVE-2022-25895/index.md)
```

## Sources

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

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