# CVE-2017-6190: Path traversal in n/a

> Remote attackers can read arbitrary files on D-Link DWR-116 routers via directory traversal in the web interface.

- **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:** 10 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cc95-94rx-4f96

## What is CVE-2017-6190?

CVE-2017-6190 is a high-severity path traversal vulnerability in n/a, published on 10 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in the web interface on the D-Link DWR-116 device with firmware before V1.05b09 allows remote attackers to read arbitrary files via a .. (dot dot) in a "GET /uir/" request.

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

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

It affects 1 product.


Products: Dlink Dwr-116 Firmware.

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

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

## Is CVE-2017-6190 being exploited?

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

Public exploit code:

- D-Link DWR-116 / DWR-116A1 - Arbitrary File Download (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6190 is a high-severity path traversal vulnerability in n/a, published on 10 Apr 2017. 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-6190 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-6190/ (Markdown: https://insights.sbomify.com/CVE-2017-6190/index.md)
```

## Sources

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

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