# CVE-2017-16130: Directory Traversal in exxxxxxxxxxx

> An attacker can read arbitrary files with extensions from the server filesystem by manipulating URL paths in the exxxxxxxxxxx Node.js module.

- **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:** 17 Sep 2024
- **Also known as:** GHSA-pq5x-rprq-8jrj

## What is CVE-2017-16130?

CVE-2017-16130 is a high-severity path traversal vulnerability in HackerOne exxxxxxxxxxx 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

exxxxxxxxxxx is an Http eX Frame Google Style JavaScript Guide. exxxxxxxxxxx is vulnerable to a directory traversal issue, giving an attacker access to the filesystem by placing "../" in the url. Accessible files are restricted to those with a file extension. Files with no extension such as /etc/passwd throw an error.

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

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

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


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

Products: Exxxxxxxxxxx Project Exxxxxxxxxxx.

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

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

## Is CVE-2017-16130 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-16130 is a high-severity path traversal vulnerability in HackerOne exxxxxxxxxxx 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-16130 in the wild and no public exploit code.

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

## Sources

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

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