dbcve.org
Residential Gateway FirmwareOperating system · Cisco

CVE-2017-11589

CRITICAL · 9.8 CVSS v3.0 Published 2017-07-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
On Cisco DDR2200 ADSL2+ Residential Gateway DDR2200B-NA-AnnexA-FCC-V00.00.03.45.4E and DDR2201v1 ADSL2+ Residential Gateway DDR2201v1-NA-AnnexA-FCC-V00.00.03.28.3 devices, there is no access control for info.html, wancfg.cmd, rtroutecfg.cmd, arpview.cmd, cpuview.cmd, memoryview.cmd, statswan.cmd, statsatm.cmd, scsrvcntr.cmd, scacccntr.cmd, logview.cmd, voicesipview.cmd, usbview.cmd, wlmacflt.cmd, wlwds.cmd, wlstationlist.cmd, HPNAShow.cmd, HPNAView.cmd, qoscls.cmd, qosqueue.cmd, portmap.cmd, scmacflt.cmd, scinflt.cmd, scoutflt.cmd, certlocal.cmd, or certca.cmd.

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 confidence

The Cisco DDR2200 and DDR2201v1 ADSL2+ Residential Gateways contain a critical authorization bypass vulnerability where multiple administrative web pages (info.html, wancfg.cmd, rtroutecfg.cmd, and 25+ others) lack any access control checks. This allows unauthenticated remote attackers to directly access sensitive management interfaces, potentially exposing system configuration, network statistics, WAN/ATM stats, QoS settings, firewall rules, certificate data, and voice/SIP settings without any credentials.

MitigationApply vendor firmware updates when available. If no update exists, implement network segmentation to restrict access to the device's management interface from untrusted networks, or replace end-of-life devices with supported hardware.

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
Residential Gateway FirmwareOperating system
Affected:= ddr2200b-na-annexa-fcc-v00.00.03.45.4e= ddr2201v1-na-annexa-fcc-v00.00.03.28.3

CVSS 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.0/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model and firmware version
    Access the device's web interface or check the administrative console for the exact model number (DDR2200 or DDR2201v1) and firmware version string. Look for version strings such as 'ddr2200b-na-annexa-fcc-v00.00.03.45.4e' or 'ddr2201v1-na-annexa-fcc-v00.00.03.28.3'.
    Affected if The device is a Cisco DDR2200 or DDR2201v1 running either of the listed firmware versions.
  2. Verify web management interface is accessible
    Attempt to reach the device's HTTP interface via its LAN or WAN IP address on common ports (80, 443, 8080). Confirm the login page loads.
    Affected if The device's web management interface is reachable on the network.
  3. Test unauthenticated access to info.html
    Navigate directly to 'http://<device_ip>/info.html' without providing any login credentials. Observe whether the page loads and displays system information.
    Affected if The page loads and displays sensitive system information without requiring authentication.
  4. Test unauthenticated access to wancfg.cmd
    Navigate directly to 'http://<device_ip>/wancfg.cmd' without logging in. Check if WAN/ATM configuration settings are exposed.
    Affected if WAN configuration settings are visible without authentication.
  5. Test unauthenticated access to rtroutecfg.cmd
    Navigate directly to 'http://<device_ip>/rtroutecfg.cmd' without logging in. Check if routing configuration is accessible.
    Affected if Routing configuration details are displayed without requiring login.

A user is affected if they have a Cisco DDR2200 or DDR2201v1 device running one of the listed firmware versions with its web management interface exposed, and any admin page loads without prompting for credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware updates when available. If no update exists, implement network segmentation to restrict access to the device's management interface from untrusted networks, or replace end-of-life devices with supported hardware.

Fix this in Residential Gateway Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-11589 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-11589 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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