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

> Remote attackers can exploit CSRF to modify DNS, firewall settings, or passwords on D-Link DSL-2730U routers.

- **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:** 6 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-f6xq-mw44-h29j

## What is CVE-2017-6411?

CVE-2017-6411 is a high-severity vulnerability in n/a, published on 6 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) on D-Link DSL-2730U C1 IN_1.00 devices allows remote attackers to change the DNS or firewall configuration or any password.

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

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

It affects 1 product.


Products: Dlink Dsl-2730u Firmware.

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

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

## Is CVE-2017-6411 being exploited?

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

Public exploit code:

- D-Link DSL-2730U Wireless N 150 - Cross-Site Request Forgery (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2023-46033](https://insights.sbomify.com/CVE-2023-46033/): Auth bypass in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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