Residential Gateway FirmwareOperating system · Cisco
CVE-2017-11587
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 · uneditedOn 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 directory traversal in the filename parameter to the /download.conf URI.
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 confidenceDirectory traversal vulnerability in the filename parameter of the /download.conf URI on Cisco DDR2200 and DDR2201v1 ADSL2+ Residential Gateways allows attackers to use '..' sequences to access files outside the web root directory.
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
= ddr2200b-na-annexa-fcc-v00.00.03.45.4e= ddr2201v1-na-annexa-fcc-v00.00.03.28.3CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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's web administration interface or check the device label/marketing materials for the model number (DDR2200 or DDR2201v1). Alternatively, inspect HTTP responses from the device for model identification strings.Affected if The device is a Cisco DDR2200 or DDR2201v1 Residential Gateway
-
Determine the firmware versionLog into the web administration panel and navigate to the status or firmware information page, or inspect the HTTP headers/responses from the device for firmware version strings such as 'v00.00.03.45.4e' or 'v00.00.03.28.3'.Affected if The installed firmware version is exactly ddr2200b-na-annexa-fcc-v00.00.03.45.4e or ddr2201v1-na-annexa-fcc-v00.00.03.28.3
-
Verify the web management interface is accessibleAttempt to access the device's IP address via HTTP (port 80) from a network-connected host. Confirm the device responds with a login page or administrative interface.Affected if The device's web interface is reachable on the network (indicating HTTP service is enabled and exposed)
-
Test for /download.conf endpoint availabilitySend an HTTP GET request to http://<device-ip>/download.conf and observe the response. A vulnerable device will return a configuration file or directory listing rather than a 404 error.Affected if The /download.conf endpoint responds with content (not 404 or access denied), indicating the vulnerable URI is available
The device is affected if it is a Cisco DDR2200 or DDR2201v1 running the specific firmware versions and the web management interface with the /download.conf endpoint is accessible on the network.
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 dataIf vendor firmware updates are unavailable (device may be end-of-life), restrict network access to the device's management interface or replace the affected gateways.
Fix this in Residential Gateway Firmware
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11587 — 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-11587 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