dbcve.org
Small Business Rv Router FirmwareApplication · Cisco

CVE-2017-3882

CRITICAL · 9.6 CVSS v3.0 Published 2017-05-16
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
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
A vulnerability in the Universal Plug-and-Play (UPnP) implementation in the Cisco CVR100W Wireless-N VPN Router could allow an unauthenticated, Layer 2-adjacent attacker to execute arbitrary code or cause a denial of service (DoS) condition. The remote code execution could occur with root privileges. The vulnerability is due to incomplete range checks of the UPnP input data, which could result in a buffer overflow. An attacker could exploit this vulnerability by sending a malicious request to the UPnP listening port of the targeted device. An exploit could allow the attacker to cause the device to reload or potentially execute arbitrary code with root privileges. This vulnerability affects all firmware releases of the Cisco CVR100W Wireless-N VPN Router prior to Firmware Release 1.0.1.22. Cisco Bug IDs: CSCuz72642.

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

Buffer overflow vulnerability in the UPnP service of Cisco CVR100W Wireless-N VPN Router allows unauthenticated, Layer 2-adjacent attackers to execute arbitrary code with root privileges or cause device reload. The flaw stems from incomplete range validation of UPnP input data, enabling specially crafted malicious packets to overflow buffers and gain code execution.

MitigationUpgrade Cisco CVR100W firmware to Release 1.0.1.22 or later. If immediate upgrade is not feasible, disable UPnP on the device as a temporary mitigation to reduce attack surface.

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
Small Business Rv Router FirmwareApplication
Affected:= 1.0.0.30= 1.0.1.9= 1.0.1.19= 1.0.2.6= 1.0.3.10= 1.0.4.10= 1.0.4.14= 1.0.5.4= 1.0.5.4\(gd\)= 1.0.5.5= 1.0.5.6= 1.0.5.8
Small Business Rv Router Firmware 1.0Application
Affected:= 0.2

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:A/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 checks

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

  1. Identify the device model
    Access the router web interface or CLI and confirm the model number is Cisco CVR100W Wireless-N VPN Router
    Affected if Device is not a Cisco CVR100W (different models are not affected by this specific CVE)
  2. Check the installed firmware version
    Navigate to the router's web interface (typically at 192.168.1.1) and look in the Administration or Status section for the firmware version. Alternatively, use the CLI command 'show version' if accessible
    Affected if Firmware version matches one of these: 1.0.0.30, 1.0.1.9, 1.0.1.19, 1.0.2.6, 1.0.3.10, 1.0.4.10, 1.0.4.14, 1.0.5.4, 1.0.5.4(gd), 1.0.5.5, 1.0.5.6, 1.0.5.8, or 1.0.0.2
  3. Verify if UPnP service is enabled
    In the router web interface, go to the UPnP settings page (usually under Advanced or Port Forwarding settings) and check whether Universal Plug and Play is turned on. If accessing via CLI, look for 'upnp enable' in the configuration
    Affected if UPnP is enabled - the vulnerability is only exploitable when the UPnP service is running

You are affected if your Cisco CVR100W runs any of the listed vulnerable firmware versions AND has UPnP service enabled.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Cisco CVR100W firmware to Release 1.0.1.22 or later. If immediate upgrade is not feasible, disable UPnP on the device as a temporary mitigation to reduce attack surface.

Recommended fix High confidence

Firmware Release 1.0.1.22 or later

  1. Access the Cisco CVR100W Wireless-N VPN Router web-based management interface
  2. Navigate to the Administration or System settings section
  3. Locate the firmware upgrade option
  4. Download firmware version 1.0.1.22 or later from the official Cisco support website
  5. Upload the firmware file to the router
  6. Wait for the upgrade process to complete and the device to reboot automatically
  7. Verify the new firmware version is installed after reboot

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Small Business Rv Router Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-3882 — 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-3882 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