# CVE-2017-18756: Misconfiguration in n/a

> Incorrect security settings in NETGEAR routers allow attackers to bypass security controls, requiring firmware updates to remediate.

- **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-645r-m8hj-xrhv

## What is CVE-2017-18756?

CVE-2017-18756 is a high-severity vulnerability in Netgear D6220 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 incorrect configuration of security settings. This affects D6220 before 1.0.0.32, D6400 before 1.0.0.66, D8500 before 1.0.3.35, DGN2200Bv4 before 1.0.0.94, DGN2200v4 before 1.0.0.94, R6250 before 1.0.4.14, R6300v2 before 1.0.4.18, R6400 before 1.01.32, R6400v2 before 1.0.2.44, R6700 before 1.0.1.36, R6900 before 1.0.1.30, R6900P before 1.3.0.8, R7000 before 1.0.9.14, R7000P before 1.3.0.8, R7100LG before 1.0.0.34, R7900 before 1.0.2.4, R8000 before 1.0.4.2, WN2500RPv2 before 1.0.1.50, WNDR3400v3 before 1.0.1.14, and WNDR4000 before 1.0.2.10.

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

It affects 19 products.


Products: Netgear D6220 Firmware, Netgear D6400 Firmware, Netgear D8500 Firmware, Netgear Dgn2200 Firmware, Netgear Dgn2200b Firmware, Netgear R6250 Firmware, Netgear R6300 Firmware, Netgear R6400 Firmware, Netgear R6700 Firmware, Netgear R6900 Firmware, Netgear R6900p Firmware, Netgear R7000 Firmware, Netgear R7000p Firmware, Netgear R7100lg Firmware, Netgear R7900 Firmware, Netgear R8000 Firmware, Netgear Wn2500rp Firmware, Netgear Wndr3400 Firmware, Netgear Wndr4000 Firmware.

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

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

## Is CVE-2017-18756 being exploited?

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

## Other vulnerabilities in Netgear D6220 Firmware

- [CVE-2016-6277](https://insights.sbomify.com/CVE-2016-6277/): NETGEAR Multiple Routers Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2021-45527](https://insights.sbomify.com/CVE-2021-45527/): Memory corruption in n/a (critical 9.6)
- [CVE-2021-45610](https://insights.sbomify.com/CVE-2021-45610/): Memory corruption in n/a (critical 9.6)
- [CVE-2021-45638](https://insights.sbomify.com/CVE-2021-45638/): Memory corruption in n/a (critical 9.6)
- [CVE-2021-34982](https://insights.sbomify.com/CVE-2021-34982/): NETGEAR Multiple Routers httpd Stack-based Buffer Overflow Remote Code Execution Vulnerability (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-18756 is a high-severity vulnerability in Netgear D6220 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-18756 in the wild and no public exploit code.

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

## Sources

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

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