Rv110w FirmwareOperating system · Cisco

CVE-2020-3150

MEDIUM · 5.9 CVSS v3.1 Published 2020-07-16
Fix available
A fix is available. Upgrade to 1.2.2.8 / 1.3.1.7 or later.
See remediation →
68/100
Remediation priority · Elevated
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
A vulnerability in the web-based management interface of Cisco Small Business RV110W and RV215W Series Routers could allow an unauthenticated, remote attacker to download sensitive information from the device, which could include the device configuration. The vulnerability is due to improper authorization of an HTTP request. An attacker could exploit this vulnerability by accessing a specific URI on the web-based management interface of the router, but only after any valid user has opened a specific file on the device since the last reboot. A successful exploit would allow the attacker to view sensitive information, which should be restricted.

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

Improper authorization in the web-based management interface of Cisco Small Business RV110W and RV215W Series Routers allows unauthenticated remote attackers to download sensitive device configuration and other restricted files by accessing a specific URI, but only after any valid user has opened a specific file on the device since the last reboot.

MitigationApply the Cisco firmware update for this vulnerability. If patching is not immediately feasible, restrict access to the router's web management interface to trusted internal networks or disable remote web management.

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 FirmwareOperating system
Affected:< 1.2.2.8
Rv215w FirmwareOperating system
Affected:< 1.3.1.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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/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 checks

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

  1. Identify device model and firmware version
    Access the router's web management interface and navigate to Status > System Summary or use CLI command 'show version' to view the firmware version
    Affected if The device is a Cisco RV110W with firmware < 1.2.2.8, or a Cisco RV215W with firmware < 1.3.1.7
  2. Check if remote web management is enabled
    Log into the router web interface and go to Firewall > Remote Management, or check via CLI under 'ip http server' or 'ip https server' settings
    Affected if Remote web management (HTTP or HTTPS) is enabled and accessible from untrusted networks
  3. Verify web service is running
    Attempt to access the router's HTTP/HTTPS ports from the WAN interface (port 80/443) or use 'show service internal' via CLI
    Affected if The web management interface responds to requests from the network where untrusted users exist

The environment is affected if the router is a vulnerable RV110W or RV215W model with firmware below the fixed versions AND the web-based management interface is accessible to untrusted 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
Upgrade available Upgrade to 1.2.2.8 / 1.3.1.7 or later
Fixed in 1.2.2.81.3.1.7
Interim mitigation

Apply the Cisco firmware update for this vulnerability. If patching is not immediately feasible, restrict access to the router's web management interface to trusted internal networks or disable remote web management.

Fix this in Rv110w Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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 locally
dbcve dependency scanner

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