CVE-2017-7576
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDragonWave 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceDragonWave Horizon Quantum wireless radios firmware 1.01.03 contain hardcoded backdoor credentials (username: 'energetic', password: 'wireless') embedded in the firmware. These credentials provide full administrative access to the device via the web interface or TELNET service, allowing attackers to compromise device configuration, monitoring, and the wireless network links it forms.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.01.03CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the device management interface or check the physical device label to confirm it is a DragonWave Horizon Quantum wireless radio. Record the exact model number for verification.Affected if The device is not a DragonWave Horizon Quantum radio (not affected by this specific CVE).
-
Check the installed firmware versionLog into the device web interface or use SNMP to retrieve the firmware version. Look for a version field typically found in the device status or system information page.Affected if The firmware version is exactly 1.01.03 (affected). Earlier or later versions are not affected by this specific hardcoded credential vulnerability.
-
Determine if TELNET service is enabledFrom an administrative workstation on the same network, run 'telnet <device-ip>' on port 23 or use a network scanner to check if port 23 is open and responding.Affected if TELNET service is enabled and accessible, as this provides a direct attack vector using the hardcoded credentials.
-
Check web management interface accessibilityAttempt to access the device web interface at http://<device-ip> from a workstation. Verify if the login page loads and is reachable.Affected if The web interface is exposed and reachable, as this is the second attack vector for exploiting the hardcoded credentials.
-
Verify the hardcoded credentials are activeAttempt to log in using the credentials username='energetic' and password='wireless' via either the web interface or TELNET. A successful login confirms the vulnerability is exploitable.Affected if The hardcoded credentials successfully authenticate, confirming the backdoor is present and exploitable.
A user is affected if they have a DragonWave Horizon Quantum radio running firmware version 1.01.03 with either TELNET or the web interface accessible on the network, and the hardcoded credentials (energetic/wireless) successfully authenticate.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade DragonWave Horizon firmware to version 1.4.8 or later to remove the hardcoded credentials. Additionally, disable TELNET access, enforce network access controls to limit web interface exposure, and monitor for unauthorized access attempts.
Firmware version 1.4.8 or later
- Identify all DragonWave Horizon wireless radio devices running firmware version 1.01.03
- Download firmware version 1.4.8 or later from the vendor's official support site
- Access each affected device through a secure management interface
- Backup current device configuration before performing firmware upgrade
- Upload and install firmware version 1.4.8 or later on each affected device
- After upgrade, verify the hardcoded credentials (energetic/wireless) no longer provide access
- Change default administrative passwords to unique, strong credentials
- Confirm the web interface and TELNET access require the new credentials
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7576 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-7576 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data