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

HIGH · 7.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 →
96/100
Remediation priority · Urgent
In the wild 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 vulnerabilities in Cisco Small Business RV160, RV260, RV340, and RV345 routers allow authenticated attackers to execute arbitrary code, elevate privileges, execute arbitrary commands, bypass authentication/authorization, fetch and run unsigned software, or cause denial of service. The specific attack vectors and affected firmware versions are not detailed in the available advisory summary.

MitigationApply the latest firmware update from Cisco's security advisory for the affected RV series routers. Restrict management interface access 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

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

CVSS:3.1/AV:L/AC:L/PR:L/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 the router model
    Access the router web interface and navigate to Administration > Device Information, or check the physical device label, or use CLI command 'show version'
    Affected if The model is RV340, RV340w, RV345, or RV345p (or RV160/RV260 if those are present in the environment)
  2. Determine installed firmware version
    In the router web interface, go to Administration > Firmware Upgrade or Administration > Device Information to view the current firmware version, or use CLI command 'show version'
    Affected if The firmware version is 1.0.03.24 or lower (any version <= 1.0.03.24)
  3. Confirm web management interface exposure
    Review firewall rules, NAT configurations, or port forwarding rules to determine if the router's HTTPS (port 443) or HTTP (port 80) management interface is accessible from WAN/untrusted networks
    Affected if The web management interface is reachable from external networks (not just LAN)
  4. Check remote management setting
    In the router web interface, navigate to Administration > Management Access and verify whether Remote Management or Allow remote access is enabled
    Affected if Remote management is enabled and the interface is WAN-accessible

The environment is affected if the router model is RV340, RV340w, RV345, or RV345p and the installed firmware version is 1.0.03.24 or lower, especially if the web management interface is exposed to 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 a release after 1.0.03.24
Interim mitigation

Apply the latest firmware update from Cisco's security advisory for the affected RV series routers. Restrict management interface access to trusted networks and monitor for indicators of compromise.

Recommended fix Moderate confidence

Latest available firmware version > 1.0.03.24 (check Cisco.com for exact version)

  1. 1. Navigate to the Cisco Software Download page for RV340, RV340w, RV345, or RV345p routers
  2. 2. Locate the latest available firmware version for your specific model
  3. 3. Review the release notes to confirm the version includes the fix for CVE-2022-20701
  4. 4. Backup your current router configuration
  5. 5. Upload and install the new firmware version following Cisco's standard firmware upgrade procedure
  6. 6. Verify the router boots successfully and all services are operational
  7. 7. Confirm the new firmware version is correctly installed
Caveat Review Cisco release notes for any configuration or feature changes between versions

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get it fixed fast

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-20701 — 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-20701 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