dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 17 Mar 2022.
Rv340 FirmwareOperating system · Cisco

CVE-2022-20700

CRITICAL · 9.8 CVSS v3.1 Published 2022-02-10
Fix available
A fix is available. Upgrade to after 1.0.03.24 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild 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 attacker to do any of the following: Execute arbitrary code Elevate privileges Execute arbitrary commands Bypass authentication and authorization protections Fetch and run unsigned software Cause denial of service (DoS) 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 (RV160, RV260, RV340, RV345) allow an attacker to potentially execute arbitrary code or commands, elevate privileges, bypass authentication mechanisms, fetch and execute unsigned software, or cause denial of service. The CVSS 9.8 score indicates trivially exploitable flaws with no authentication required.

MitigationApply Cisco's available firmware updates for the RV series routers; until patched, restrict network access to router management interfaces and monitor for unauthorized changes.

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
Rv340 FirmwareOperating system
Affected:<= 1.0.03.24
Rv340w FirmwareOperating system
Affected:<= 1.0.03.24
Rv345 FirmwareOperating system
Affected:<= 1.0.03.24
Rv345p FirmwareOperating system
Affected:<= 1.0.03.24
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

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 router model
    Log into the router web interface or CLI and locate the device model identifier (RV160, RV160W, RV260, RV260P, RV340, RV340W, RV345, or RV345P)
    Affected if Model is any of the eight listed RV series routers (RV160/RV160W/RV260/RV260P/RV340/RV340W/RV345/RV345P)
  2. Check firmware version via web interface
    Navigate to Status or General page in the router admin UI to view the current firmware version
    Affected if Firmware version cannot be determined or is not visible in the interface
  3. Check firmware version via CLI
    Connect to the router CLI and run the command: show version
    Affected if Cannot access CLI or version command fails to return firmware information
  4. Compare RV340/345 firmware to affected version
    If model is RV340, RV340W, RV345, or RV345P, compare your firmware version to 1.0.03.24 - any version at or below 1.0.03.24 is affected
    Affected if Firmware version is 1.0.03.24 or lower on RV340/RV340W/RV345/RV345P
  5. Compare RV160/260 firmware to affected version
    If model is RV160, RV160W, RV260, or RV260P, compare your firmware version to 1.0.01.05 - any version at or below 1.0.01.05 is affected
    Affected if Firmware version is 1.0.01.05 or lower on RV160/RV160W/RV260/RV260P

You are affected if your router model is one of the eight listed RV series models AND your installed firmware version falls at or below the threshold for your specific model (1.0.01.05 for RV160/RV260 series or 1.0.03.24 for RV340/RV345 series).

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 a release after 1.0.03.24
Interim mitigation

Apply Cisco's available firmware updates for the RV series routers; until patched, restrict network access to router management interfaces and monitor for unauthorized changes.

Fix this in Rv340 Firmware Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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