# CVE-2017-16523: Hardcoded credentials in n/a

> Undocumented root-equivalent credentials allow attackers to gain full administrative control over affected MitraStar routers.

- **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:** 3 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mp3c-h87m-phrj

## What is CVE-2017-16523?

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

### Official description

MitraStar GPT-2541GNAC (HGU) 1.00(VNJ0)b1 and DSL-100HN-T1 ES_113WJY0b16 devices have a zyad1234 password for the zyad1234 account, which is equivalent to root and undocumented.

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

It affects 2 products.


Products: Mitrastar Dsl-100hn-T1 Firmware, Mitrastar Gpt-2541gnac Firmware.

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

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

## Is CVE-2017-16523 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-16522](https://insights.sbomify.com/CVE-2017-16522/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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