dbcve.org
Rv160 FirmwareOperating system · Cisco

CVE-2022-20827

CRITICAL · 10.0 CVSS v3.1 Published 2022-08-10
Fix available
A fix is available. Upgrade to 1.0.01.05 / 1.0.03.26 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
Multiple vulnerabilities in Cisco Small Business RV160, RV260, RV340, and RV345 Series Routers could allow an unauthenticated, remote attacker to execute arbitrary code or cause a denial of service (DoS) condition on an affected device. For more information about these vulnerabilities, see the Details section of this advisory.

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 · moderate confidence

Multiple critical vulnerabilities in Cisco Small Business RV series routers allow unauthenticated remote attackers to execute arbitrary code or cause denial of service. The CVSS 10 score indicates trivial network-based exploitation without authentication, leading to complete device compromise.

MitigationApply the Cisco firmware updates for RV160, RV260, RV340, and RV345 series routers as specified in the Cisco security advisory. If patching is not immediately feasible, restrict management interface exposure to trusted networks or disable remote management if not required.

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
Rv160 FirmwareOperating system
Affected:< 1.0.01.05
Rv160w FirmwareOperating system
Affected:< 1.0.01.05
Rv260 FirmwareOperating system
Affected:< 1.0.01.05
Rv260p FirmwareOperating system
Affected:< 1.0.01.05
Rv260w FirmwareOperating system
Affected:< 1.0.01.05
Rv340 FirmwareOperating system
Affected:< 1.0.03.26
Rv340w FirmwareOperating system
Affected:< 1.0.03.26
Rv345 FirmwareOperating system
Affected:< 1.0.03.26

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 router model
    Access the router web interface or CLI and locate the device model number (RV160, RV160w, RV260, RV260p, RV260w, RV340, RV340w, or RV345). In the web interface, this is typically found under Status or Device Info pages. Via CLI, use 'show version' or 'show system-info'.
    Affected if The device is one of these models: RV160, RV160w, RV260, RV260p, RV260w, RV340, RV340w, or RV345.
  2. Determine the installed firmware version
    In the router web interface, go to Administration or Firmware page to view the current firmware version. Via CLI, use 'show version' command which displays the firmware build and version number.
    Affected if The firmware version cannot be determined or is not visible in the device management interface.
  3. Compare RV160/RV260 firmware to affected range
    For RV160, RV160w, RV260, RV260p, or RV260w models, check if the firmware version is lower than 1.0.01.05. Compare the version string exactly, noting that versions like 1.0.00.12, 1.0.01.04, or any build below 1.0.01.05 are vulnerable.
    Affected if The device is an RV160/RV260 series and the firmware version starts with a number lower than 1.0.01.05 (for example, 1.0.01.04 or earlier), or the version begins with 1.0.00.x.
  4. Compare RV340/RV345 firmware to affected range
    For RV340, RV340w, or RV345 models, check if the firmware version is lower than 1.0.03.26. Compare the version string exactly, noting that versions like 1.0.03.25, 1.0.03.20, or any build below 1.0.03.26 are vulnerable.
    Affected if The device is an RV340/RV345 series and the firmware version is below 1.0.03.26 (for example, 1.0.03.25 or earlier).

A user is affected if they have a Cisco RV series router (RV160/RV260 or RV340/RV345) running firmware version below the respective thresholds (1.0.01.05 for RV160/RV260 series, 1.0.03.26 for RV340/RV345 series), as these versions contain the vulnerabilities that allow unauthenticated remote code execution.

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.0.01.05 / 1.0.03.26 or later
Fixed in 1.0.01.051.0.03.26
Interim mitigation

Apply the Cisco firmware updates for RV160, RV260, RV340, and RV345 series routers as specified in the Cisco security advisory. If patching is not immediately feasible, restrict management interface exposure to trusted networks or disable remote management if not required.

Recommended fix High confidence

Rv160/Rv160w/Rv260/Rv260p/Rv260w: firmware 1.0.01.05 or later | Rv340/Rv340w/Rv345: firmware 1.0.03.26 or later

  1. 1. Identify the exact router model (RV160, RV160w, RV260, RV260p, RV260w, RV340, RV340w, or RV345) from the device label or web interface.
  2. 2. Access the Cisco software download page at cisco.com and navigate to the downloads for your specific router model.
  3. 3. Download firmware version 1.0.01.05 or later for RV160/RV260 series routers, or version 1.0.03.26 or later for RV340/RV345 series routers.
  4. 4. Access the router's web-based management interface by entering the device IP address in a browser.
  5. 5. Navigate to Administration > Firmware Upgrade or similar firmware upload section.
  6. 6. Click Upload or Browse to select the downloaded firmware file, then click Upgrade or Apply.
  7. 7. Wait for the firmware upload and installation to complete - do not power off the device during this process.
  8. 8. After reboot, log back into the router interface and verify the firmware version under Status or Administration > Firmware Upgrade to confirm the fix is applied.
Caveat Standard firmware upgrade risks apply - ensure stable power during upload; back up configuration before upgrading; some settings may reset to defaults requiring reconfiguration

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

Fix this in Rv160 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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