# CVE-2017-9466: Weak cryptography in n/a

> Weak DES encryption in TP-Link WR841N routers allows attackers to bypass access controls and modify system settings via LAN or Wi-Fi.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 26 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5m39-qpvm-r38g

## What is CVE-2017-9466?

CVE-2017-9466 is a critical vulnerability in n/a, published on 26 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The executable httpd on the TP-Link WR841N V8 router before TL-WR841N(UN)_V8_170210 contained a design flaw in the use of DES for block encryption. This resulted in incorrect access control, which allowed attackers to gain read-write access to system settings through the protected router configuration service tddp via the LAN and Ath0 (Wi-Fi) interfaces.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

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

It affects 1 product.


Products: Tp-Link Wr841n V8 Firmware.

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

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

## Is CVE-2017-9466 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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