# CVE-2017-17065: Denial of service in n/a

> An attacker can crash the D-Link DIR-605L router by sending an overly long password in HNAP authentication requests.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-m47j-8m4h-p58q

## What is CVE-2017-17065?

CVE-2017-17065 is a high-severity denial of service vulnerability in n/a, published on 30 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on D-Link DIR-605L Model B before FW2.11betaB06_hbrf devices, related to the code that handles the authentication values for HNAP. An attacker can cause a denial of service (device crash) or possibly have unspecified other impact by sending a sufficiently long string in the password field of the HTTP Basic Authentication section of the HTTP request.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Dlink Dir-605l Model B Firmware.

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

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

## Is CVE-2017-17065 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17065 is a high-severity denial of service vulnerability in n/a, published on 30 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-17065 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-17065/ (Markdown: https://insights.sbomify.com/CVE-2017-17065/index.md)
```

## Sources

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

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