# CVE-2016-10401: Hardcoded credentials in n/a

> Hardcoded root password allows remote attackers to gain root access on ZyXEL PK5001Z devices if a non-root account is compromised.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jul 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2f5j-3w2j-7mxv

## What is CVE-2016-10401?

CVE-2016-10401 is a high-severity vulnerability in n/a, published on 25 Jul 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ZyXEL PK5001Z devices have zyad5001 as the su password, which makes it easier for remote attackers to obtain root access if a non-root account password is known (or a non-root default account exists within an ISP's deployment of these devices).

Weakness: CWE-255

## Which versions are affected by CVE-2016-10401?

It affects 1 product.


Products: Zyxel Pk5001z Firmware.

## How do I fix CVE-2016-10401?

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

## Is CVE-2016-10401 being exploited?

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

Public exploit code:

- ZyXEL PK5001Z Modem - Backdoor Account (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-10401 and fix it if it is affected.

What it is: CVE-2016-10401 is a high-severity vulnerability in n/a, published on 25 Jul 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-10401 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-2016-10401/ (Markdown: https://insights.sbomify.com/CVE-2016-10401/index.md)
```

## Sources

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

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