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

> Hardcoded vendor credentials in DragonWave Horizon wireless radios allow attackers to gain administrative access via web or Telnet interfaces.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 6 Apr 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-2pw8-g87h-mhmj

## What is CVE-2017-7576?

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

### Official description

DragonWave Horizon 1.01.03 wireless radios have hardcoded login credentials (such as the username of energetic and password of wireless) meant to allow the vendor to access the devices. These credentials can be used in the web interface or by connecting to the device via TELNET. This is fixed in recent versions including 1.4.8.

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

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

It affects 1 product.


Products: Dragonwavex Horizon Wireless Radio Firmware.

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

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

## Is CVE-2017-7576 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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