dbcve.org
Rv110w Wireless N Vpn Firewall FirmwareOperating system · Cisco

CVE-2020-3330

CRITICAL · 9.8 CVSS v3.1 Published 2020-07-16
Fix available
A fix is available. Upgrade to 1.2.2.8 or later.
See remediation →
100/100
Remediation priority · Urgent
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 Telnet service of Cisco Small Business RV110W Wireless-N VPN Firewall Routers could allow an unauthenticated, remote attacker to take full control of the device with a high-privileged account. The vulnerability exists because a system account has a default and static password. An attacker could exploit this vulnerability by using this default account to connect to the affected system. A successful exploit could allow the attacker to gain full control of an affected device.

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

A vulnerability exists in the Telnet service of Cisco Small Business RV110W Wireless-N VPN Firewall Routers where a system account has a default static password. An unauthenticated remote attacker can use this known credential to connect via Telnet and gain full administrative (high-privileged) control of the affected device.

MitigationApply the Cisco firmware update for RV110W when available, or disable the Telnet service if not required for business operations. If Telnet must remain enabled, restrict network access to trusted management stations via ACLs or VPN.

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
Affected:< 1.2.2.8

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

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

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

  1. Identify device model
    Access the router web interface or console and verify the model number is Cisco RV110W Wireless-N VPN Firewall. Check the device label or system information page.
    Affected if Device is not a Cisco RV110W model - not affected by this specific CVE
  2. Check firmware version
    Log into the router web interface, navigate to Status > System Summary, or use the command line and run 'show version' to display the firmware version. Compare against the vulnerable range.
    Affected if Firmware version is 1.2.2.8 or higher - not affected; version < 1.2.2.8 is vulnerable
  3. Verify Telnet service status
    Access router administration interface, navigate to Firewall > Service Management or similar, or use CLI command 'show service' to check if Telnet service is enabled.
    Affected if Telnet service is enabled and accessible - device is vulnerable to unauthenticated remote access
  4. Assess network exposure
    Check router firewall rules or ACLs to determine if TCP port 23 (Telnet) is open to untrusted networks (WAN/internet). Use port scan from external IP or review firewall configuration.
    Affected if Telnet port 23 is exposed to untrusted/internet-facing networks - remote exploitation is possible

Device is affected only if it is an RV110W router running firmware below version 1.2.2.8 with Telnet service enabled and accessible from untrusted networks.

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
Upgrade available Upgrade to 1.2.2.8 or later
Fixed in 1.2.2.8
Interim mitigation

Apply the Cisco firmware update for RV110W when available, or disable the Telnet service if not required for business operations. If Telnet must remain enabled, restrict network access to trusted management stations via ACLs or VPN.

Recommended fix High confidence

RV110W firmware version 1.2.2.8 or later

  1. 1. Download the latest firmware version 1.2.2.8 or later from the Cisco website
  2. 2. Access the router's web-based management interface
  3. 3. Navigate to Administration > Firmware Upgrade
  4. 4. Click Browse and select the downloaded firmware file
  5. 5. Click Upload to begin the firmware upgrade process
  6. 6. Wait for the upgrade to complete and the device to reboot
  7. 7. Verify the firmware version has been updated in the router's status page
  8. 8. Change any default credentials after the upgrade as a security best practice
Caveat Router will reboot during upgrade; ensure no critical traffic is passing through during the maintenance window

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

Fix this in Rv110w Wireless N Vpn Firewall Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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