Rv110w Wireless N Vpn Firewall FirmwareOperating system · Cisco
CVE-2015-6397
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 · uneditedCisco RV110W, RV130W, and RV215W devices have an incorrect RBAC configuration for the default account, which allows remote authenticated users to obtain root access via a login session with that account, aka Bug IDs CSCuv90139, CSCux58175, and CSCux73557.
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 Cisco RV110W, RV130W, and RV215W routers have a Role-Based Access Control (RBAC) misconfiguration that allows the default administrative account to escalate privileges to root access. An authenticated remote user leveraging this vulnerable default account can obtain full root privileges on the affected device.
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
Rv110w Wireless N Vpn Firewall FirmwareOperating system
all versions
Rv130w Wireless N Multifunction Vpn Router FirmwareOperating system
all versions
Rv215w Wireless N Vpn Router FirmwareOperating system
all versionsCVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify router modelAccess the device web interface or CLI and confirm the exact model number is Cisco RV110W, RV130W, or RV215WAffected if The device model is one of RV110W, RV130W, or RV215W
-
Check firmware versionNavigate to the device status or firmware upgrade page in the web interface, or run 'show version' command via CLIAffected if Any firmware version is installed on these models (all versions are affected)
-
Verify default administrative account statusNavigate to User Management or Administration settings in the web interface and confirm if the default 'admin' account exists and is enabledAffected if The default admin account is present and active on the device
-
Check management interface exposureExamine the device network settings to determine if the management interface (HTTP/HTTPS/SSH) is accessible from WAN/external networksAffected if Remote management is enabled and the admin interface is reachable from untrusted networks
If your device is a Cisco RV110W, RV130W, or RV215W with the default admin account enabled and accessible (especially from remote networks), you are affected by this RBAC privilege escalation vulnerability.
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 dataApply the Cisco firmware updates addressing CSCuv90139, CSCux58175, and CSCux73557. If patching is not immediately feasible, restrict management interface access to trusted networks and monitor for unauthorized access.
Fix this in Rv110w Wireless N Vpn Firewall Firmware
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6397 — 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-2015-6397 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