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

> Attackers can read arbitrary files on vulnerable NETGEAR routers, exposing sensitive information.

- **Severity:** High 8.8 (`CVSS:3.0/AC:L/AV:A/A:H/C:H/I:H/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Apr 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h8h3-697g-vpc3

## What is CVE-2017-18752?

CVE-2017-18752 is a high-severity path traversal vulnerability in Netgear R6300 Firmware, published on 22 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Certain NETGEAR devices are affected by an attacker's ability to read arbitrary files. This affects EX3700 before 1.0.0.64, EX3800 before 1.0.0.64, EX6120 before 1.0.0.32, EX6130 before 1.0.0.16, R6300v2 before 1.0.4.12, R6700 before 1.0.1.26, R6900 before 1.0.1.22, R7000 before 1.0.9.6, R7300DST before 1.0.0.52, R7900 before 1.0.1.12, R8000 before 1.0.3.24, and R8500 before 1.0.2.94.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 12 products.


Products: Netgear Ex3700 Firmware, Netgear Ex3800 Firmware, Netgear Ex6120 Firmware, Netgear Ex6130 Firmware, Netgear R6300 Firmware, Netgear R6700 Firmware, Netgear R6900 Firmware, Netgear R7000 Firmware, Netgear R7300dst Firmware, Netgear R7900 Firmware, Netgear R8000 Firmware, Netgear R8500 Firmware.

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

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

## Is CVE-2017-18752 being exploited?

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

## Other vulnerabilities in Netgear R6300 Firmware

- [CVE-2021-32122](https://insights.sbomify.com/CVE-2021-32122/): Cross-site request forgery in n/a (critical 9.8)
- [CVE-2017-18747](https://insights.sbomify.com/CVE-2017-18747/): Misconfiguration in n/a (high 8.8)
- [CVE-2017-18772](https://insights.sbomify.com/CVE-2017-18772/): Auth bypass in n/a (high 8.8)
- [CVE-2025-5934](https://insights.sbomify.com/CVE-2025-5934/): Netgear EX3700 mtd sub_41619C stack-based overflow (high 8.7)
- [CVE-2024-35519](https://insights.sbomify.com/CVE-2024-35519/): Command injection in n/a (high 8.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-18752 is a high-severity path traversal vulnerability in Netgear R6300 Firmware, published on 22 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-18752 in the wild and no public exploit code.

Affected product: Netgear R6300 Firmware. 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-18752/ (Markdown: https://insights.sbomify.com/CVE-2017-18752/index.md)
```

## Sources

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

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