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

> Attackers can bypass authentication and perform unauthorized actions on NETGEAR routers via CSRF, requiring firmware updates.

- **Severity:** High 8.4 (`CVSS:3.0/AC:L/AV:L/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:** 20 Apr 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-pwr4-4q52-jj45

## What is CVE-2017-18852?

CVE-2017-18852 is a high-severity vulnerability in Netgear R7300dst Firmware, published on 20 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 CSRF and authentication bypass. This affects R7300DST before 1.0.0.54, R8300 before 1.0.2.100_1.0.82, R8500 before 1.0.2.100_1.0.82, and WNDR3400v3 before 1.0.1.14.

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

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

It affects 4 products.


Products: Netgear R7300dst Firmware, Netgear R8300 Firmware, Netgear R8500 Firmware, Netgear Wndr3400 Firmware.

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

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

## Is CVE-2017-18852 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-18852 is a high-severity vulnerability in Netgear R7300dst Firmware, published on 20 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-18852 in the wild and no public exploit code.

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

## Sources

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

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