CVE-2017-7964
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 · uneditedZyxel WRE6505 devices have a default TELNET password of 1234 for the root and admin accounts, which makes it easier for remote attackers to conduct DNS hijacking attacks by reconfiguring the built-in dnshijacker process.
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 confidenceThe Zyxel WRE6505 wireless range extender ships with a hardcoded default TELNET password of '1234' for both root and admin accounts. This allows remote attackers to gain full administrative access to the device via TELNET and reconfigure the built-in dnshijacker process to intercept and manipulate DNS queries from connected clients.
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<= v1.00\(aaqb.3\)c0CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/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 web interface or check the physical device label to confirm it is a Zyxel WRE6505 wireless range extenderAffected if The device is not a Zyxel WRE6505, then this specific CVE does not apply
-
Check the firmware versionLog into the device web interface and navigate to the Status or Management page to view the firmware version, or use the TELNET/SSH interface and run the command to display firmware version (commonly 'sysversion' or check boot log)Affected if The firmware version is v1.00(aaqb.3)c0 or earlier (any version <= v1.00(aaqb.3)c0)
-
Verify if TELNET service is enabledCheck the device configuration through the web interface under Services or Firewall settings to see if TELNET access is permitted, or attempt to connect to the device on port 23 (TELNET) from an authorized network segmentAffected if TELNET service is enabled and accessible on the device
-
Confirm default credentials are in useAttempt to authenticate via TELNET using the username 'root' or 'admin' with password '1234', or check the device user configuration through the web interface to see if the default password remains unchangedAffected if The default password '1234' is still configured for either the root or admin account
You are affected if you own a Zyxel WRE6505 device running firmware version v1.00(aaqb.3)c0 or earlier, with TELNET enabled and the default password '1234' still in use.
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.
From vendor dataChange the default TELNET password immediately to a strong, unique credential and disable the TELNET service if not required, or restrict access to trusted IP addresses only.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7964 — 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-7964 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