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

> An attacker can reset the admin password on TP-Link Archer C9 routers due to a predictable random number generator seed, leading to full device compromise.

- **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:** 21 Jul 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-frjm-wvvg-4gw5

## What is CVE-2017-11519?

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

### Official description

passwd_recovery.lua on the TP-Link Archer C9(UN)_V2_160517 allows an attacker to reset the admin password by leveraging a predictable random number generator seed. This is fixed in C9(UN)_V2_170511.

Weakness: CWE-335 (Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG))

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

It affects 1 product.


Products: Tp-Link Archer C9 \(2.0\) Firmware.

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

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

## Is CVE-2017-11519 being exploited?

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

Public exploit code:

- POC for TP-Link Archer C9 - Admin Password Reset and RCE (CVE-2017-11519) (github_poc): https://github.com/vakzz/tplink-CVE-2017-11519

## Fix prompt for AI coding agents

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

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

## Sources

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

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