# CVE-2017-18703: Cross-site request forgery in n/a

> Attackers can perform unauthorized actions on NETGEAR routers via CSRF, requiring firmware upgrades to mitigate.

- **Severity:** High 8.8 (`CVSS:3.0/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:R`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Apr 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-fqqw-qmp7-4hh9

## What is CVE-2017-18703?

CVE-2017-18703 is a high-severity vulnerability in Netgear D6100 Firmware, published on 24 Apr 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Certain NETGEAR devices are affected by CSRF. This affects D1500 before 1.0.0.25, D500 before 1.0.0.25, D6100 before 1.0.0.55, D7000 before 1.0.1.50, D7800 before 1.0.1.28, EX6100v2 before 1.0.1.60, EX6150v2 before 1.0.1.60, JNR1010v2 before 1.1.0.46, JR6150 before 1.0.1.16, JWNR2010v5 before 1.1.0.46, PR2000 before 1.0.0.18, R6020 before 1.0.0.26, R6050 before 1.0.1.16, R6080 before 1.0.0.26, R6100 before 1.0.1.20, R6220 before 1.1.0.60, R7500 before 1.0.0.118, R7500v2 before 1.0.3.20, R7800 before 1.0.2.40, R9000 before 1.0.2.52, WN3000RPv3 before 1.0.2.50, WN3100RPv2 before 1.0.0.40, WNDR3700v5 before 1.1.0.48, WNDR4300v2 before 1.0.0.48, WNDR4500v3 before 1.0.0.48, WNR1000v4 before 1.1.0.46, WNR2000v5 before 1.0.0.62, WNR2020 before 1.1.0.46, and WNR2050 before 1.1.0.46.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 28 products.


Products: Netgear D1500 Firmware, Netgear D500 Firmware, Netgear D6100 Firmware, Netgear D7000 Firmware, Netgear D7800 Firmware, Netgear Ex6100 Firmware, Netgear Ex6150 Firmware, Netgear Jnr1010 Firmware, Netgear Jr6150 Firmware, Netgear Jwnr2010 Firmware, Netgear Pr2000 Firmware, Netgear R6020 Firmware, Netgear R6050 Firmware, Netgear R6080 Firmware, Netgear R6100 Firmware, Netgear R6220 Firmware, Netgear R7500 Firmware, Netgear R7800 Firmware, Netgear R9000 Firmware, Netgear Wn3000rp Firmware and 8 more.

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

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

## Is CVE-2017-18703 being exploited?

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

## Other vulnerabilities in Netgear D6100 Firmware

- [CVE-2017-18798](https://insights.sbomify.com/CVE-2017-18798/): Misconfiguration in n/a (high 8.4)
- [CVE-2018-21139](https://insights.sbomify.com/CVE-2018-21139/): Information disclosure in n/a (high 7.1)
- [CVE-2018-21230](https://insights.sbomify.com/CVE-2018-21230/): Misconfiguration in n/a (medium 5.2)
- [CVE-2018-21231](https://insights.sbomify.com/CVE-2018-21231/): Misconfiguration in n/a (medium 5.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-18703 is a high-severity vulnerability in Netgear D6100 Firmware, published on 24 Apr 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-18703 in the wild and no public exploit code.

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

## Sources

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

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