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

> Remote attackers can hijack user authentication to perform DNS lookups, potentially leading to remote code execution when combined with another vulnerability.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 15 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-f99c-gfmc-7mwv

## What is CVE-2017-6366?

CVE-2017-6366 is a high-severity vulnerability in n/a, published on 15 Mar 2017. 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

Cross-site request forgery (CSRF) vulnerability in NETGEAR DGN2200 routers with firmware 10.0.0.20 through 10.0.0.50 allows remote attackers to hijack the authentication of users for requests that perform DNS lookups via the host_name parameter to dnslookup.cgi. NOTE: this issue can be combined with CVE-2017-6334 to execute arbitrary code remotely.

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

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

It affects 1 product.


Products: Netgear Dgn2200 Firmware.

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

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

## Is CVE-2017-6366 being exploited?

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

Public exploit code:

- Netgear DGN2200v1/v2/v3/v4 - Cross-Site Request Forgery (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2017-6077](https://insights.sbomify.com/CVE-2017-6077/): NETGEAR DGN2200 Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-17373](https://insights.sbomify.com/CVE-2019-17373/): Auth bypass in n/a (critical 9.8)
- [CVE-2016-5649](https://insights.sbomify.com/CVE-2016-5649/): Netgear DGN2200 and DGND3700 disclose the administrator password (critical 9.8)
- [CVE-2024-57046](https://insights.sbomify.com/CVE-2024-57046/): Auth bypass in n/a (high 8.8)
- [CVE-2017-18755](https://insights.sbomify.com/CVE-2017-18755/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6366 is a high-severity vulnerability in n/a, published on 15 Mar 2017. 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-6366 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-2017-6366/ (Markdown: https://insights.sbomify.com/CVE-2017-6366/index.md)
```

## Sources

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

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