Rv215w Wireless N Vpn Router FirmwareOperating system · Cisco

CVE-2016-1397

MEDIUM · 6.5 CVSS v3.0 Published 2016-06-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Buffer overflow in the web-based management interface on Cisco RV110W devices with firmware before 1.2.1.7, RV130W devices with firmware before 1.0.3.16, and RV215W devices with firmware before 1.3.0.8 allows remote authenticated users to cause a denial of service (device reload) via crafted configuration commands in an HTTP request, aka Bug ID CSCux82523.

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 in the web-based management interface on Cisco RV110W, RV130W, and RV215W routers allows remote authenticated users to cause denial of service via crafted configuration commands in HTTP requests, triggering device reload.

MitigationUpgrade firmware to the latest version (RV110W: 1.2.1.7+, RV130W: 1.0.3.16+, RV215W: 1.3.0.8+). If immediate upgrade is not feasible, restrict web management interface access to trusted IP addresses or networks only.

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
Rv215w Wireless N Vpn Router FirmwareOperating system
Affected:= 1.1.0.5= 1.1.0.6= 1.2.0.14= 1.2.0.15= 1.3.0.7
Rv110w Wireless N Vpn Firewall FirmwareOperating system
Affected:= 1.1.0.9= 1.2.0.9= 1.2.0.10= 1.2.1.4
Rv130w Wireless N Multifunction Vpn Router FirmwareOperating system
Affected:= 1.0.0.21= 1.0.1.3= 1.0.2.7

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 router model
    Log into the device web interface or check the device label to confirm the model is RV110W, RV130W, or RV215W
    Affected if Model is one of RV110W, RV130W, or RV215W
  2. Check firmware version
    Access the router web interface, navigate to Status or System Summary page to view the firmware version, or use the command line and run 'show version'
    Affected if Firmware version matches 1.1.0.5, 1.1.0.6, 1.2.0.14, 1.2.0.15, 1.3.0.7 (RV215W); 1.1.0.9, 1.2.0.9, 1.2.0.10, 1.2.1.4 (RV110W); or 1.0.0.21, 1.0.1.3, 1.0.2.7 (RV130W)
  3. Verify web-based management is enabled
    In the router web interface, go to Administration or Management settings and check if HTTP/HTTPS management access is enabled
    Affected if Web-based management interface is enabled and accessible
  4. Check remote access configuration
    In the router web interface, examine the management access settings to determine if remote (WAN) access to the web interface is permitted
    Affected if Remote authenticated users can access the web management interface from outside the local network

The device is affected if it is an RV110W, RV130W, or RV215W router running one of the listed firmware versions AND the web-based management interface is accessible to remote authenticated users.

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

Upgrade firmware to the latest version (RV110W: 1.2.1.7+, RV130W: 1.0.3.16+, RV215W: 1.3.0.8+). If immediate upgrade is not feasible, restrict web management interface access to trusted IP addresses or networks only.

Fix this in Rv215w Wireless N Vpn Router Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-1397 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-1397 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