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-20703

HIGH · 8.0 CVSS v3.1 Published 2022-02-10
Fix available
A fix is available. Upgrade to after 1.0.03.24 or later.
See remediation →
97/100
Remediation priority · Urgent
In the wild No privileges

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 exist in Cisco Small Business RV160, RV260, RV340, and RV345 Series Routers firmware. These vulnerabilities allow remote attackers to execute arbitrary code or commands, elevate privileges, bypass authentication mechanisms, fetch and execute unsigned software, or cause denial of service. The attack vector appears to be network-adjacent or remote, exploiting weaknesses in the router firmware's input validation, authentication, or authorization logic.

MitigationApply the Cisco firmware updates for the affected RV series routers as soon as they become available. Until patches are applied, limit router management interface exposure to trusted networks and monitor for indicators of compromise.

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
Adjacent
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:R/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 number (RV160, RV160w, RV260, RV260p, RV340, RV340w, RV345, or RV345p)
    Affected if Router model is one of the RV series models listed in the affected products
  2. Check firmware version via web interface
    Navigate to the router administration page, typically at https://[router-ip]/ and look for a Status or System Summary page that displays the firmware version
    Affected if Firmware version cannot be determined or does not display clearly
  3. Check firmware version via CLI
    Access router via SSH or console, log in, and run the command 'show version' or 'get system version' to retrieve the firmware build number
    Affected if CLI access is unavailable and web interface version display is unclear
  4. Compare version against affected ranges
    Compare your installed firmware version to: RV340/RV340w/RV345/RV345p = 1.0.03.24 or lower; RV160/RV160w/RV260/RV260p = 1.0.01.05 or lower
    Affected if Installed version is at or below the threshold for your specific model (e.g., 1.0.03.24 or lower for RV340/RV345 series, 1.0.01.05 or lower for RV160/RV260 series)
  5. Verify management interface exposure
    Check router network settings to determine if the management web interface (HTTP/HTTPS) or SSH is accessible from WAN or untrusted networks rather than only from trusted LAN segments
    Affected if Management interface is reachable from WAN or untrusted networks (this increases exposure risk for the vulnerabilities)

You are affected if your router is an RV160, RV260, RV340, or RV345 model running firmware at or below the version thresholds (1.0.01.05 for RV160/RV260 series, 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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.0.03.24
Interim mitigation

Apply the Cisco firmware updates for the affected RV series routers as soon as they become available. Until patches are applied, limit router management interface exposure to trusted networks and monitor for indicators of compromise.

Recommended fix High confidence

Firmware newer than 1.0.03.24 for RV340/RV345 series; Firmware newer than 1.0.01.05 for RV160/RV260 series (consult Cisco advisory for exact fixed release)

  1. Identify the exact model of Cisco Small Business router from the RV160, RV260, RV340, or RV345 series
  2. Access the Cisco Software Downloads page for your specific router model
  3. Download the latest available firmware version that addresses security vulnerabilities
  4. Follow Cisco's standard firmware upgrade procedure: backup current configuration, upload new firmware via web UI or CLI, verify upgrade integrity, restore configuration if needed
  5. After upgrade, verify the router is functioning normally and the vulnerability is remediated
Caveat Review Cisco release notes for any configuration or feature changes between versions; backup configuration before upgrading

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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