# CVE-2016-4815: Path traversal in n/a

> Remote attackers can read arbitrary files on Buffalo WZR-600DHP3 and WZR-S600DHP routers via a directory traversal vulnerability.

- **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:** 19 Jun 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5f7h-72v6-mhp9

## What is CVE-2016-4815?

CVE-2016-4815 is a high-severity path traversal vulnerability in n/a, published on 19 Jun 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability on BUFFALO WZR-600DHP3 devices with firmware 2.16 and earlier and WZR-S600DHP devices with firmware 2.16 and earlier allows remote attackers to read arbitrary files via unspecified vectors.

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

## Which versions are affected by CVE-2016-4815?

It affects 6 products.


Products: Buffalo Wzr-600dhp2 Firmware, Buffalo Wzr-600dhp3 Firmware, Buffalo Wzr-900dhp2 Firmware, Buffalo Wzr-900dhp Firmware, Buffalo Wzr-S600dhp Firmware, Buffalo Wzr-S900dhp Firmware.

## How do I fix CVE-2016-4815?

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

## Is CVE-2016-4815 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-4815 and fix it if it is affected.

What it is: CVE-2016-4815 is a high-severity path traversal vulnerability in n/a, published on 19 Jun 2016. 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-2016-4815 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-2016-4815/ (Markdown: https://insights.sbomify.com/CVE-2016-4815/index.md)
```

## Sources

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

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