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

> Attackers can log in via telnet using default root credentials to read, write, and execute code on the device.

- **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:** 20 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mfpf-xpqg-f44w

## What is CVE-2017-8772?

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

### Official description

On BE126 WIFI repeater 1.0 devices, an attacker can log into telnet (which is open by default) with default credentials as root (username:"root" password:"root") and can: 1. Read the entire file system; 2. Write to the file system; or 3. Execute any code that attacker desires (malicious or not).

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Twsz Wifi Repeater Firmware.

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

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

## Is CVE-2017-8772 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-8771](https://insights.sbomify.com/CVE-2017-8771/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2017-13713](https://insights.sbomify.com/CVE-2017-13713/): Command injection in n/a (high 8.8)
- [CVE-2017-8770](https://insights.sbomify.com/CVE-2017-8770/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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