# CVE-2017-16169: Directory Traversal in looppake

> An attacker can read arbitrary files from the server filesystem by exploiting a directory traversal vulnerability in the looppake HTTP server library.

- **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:** 7 Jun 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-4vfj-c2xf-8r48

## What is CVE-2017-16169?

CVE-2017-16169 is a high-severity path traversal vulnerability in HackerOne looppake node module, published on 7 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

looppake is a simple http server. looppake is vulnerable to a directory traversal issue, giving an attacker access to the filesystem by placing "../" in the url.

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

## Which versions are affected by CVE-2017-16169?

2 open source packages ship an affected version, including looppake. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `looppake` | npm | All versions to 3.0.0 | None |
| `looppake` | npm | All versions to 3.0.0 | None |

Products: Looppake Project Looppake.

## How do I fix CVE-2017-16169?

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

## Is CVE-2017-16169 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-16169 and fix it if it is affected.

What it is: CVE-2017-16169 is a high-severity path traversal vulnerability in HackerOne looppake node module, published on 7 Jun 2018. 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-2017-16169 in the wild and no public exploit code.

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

## Sources

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

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