Rv340 FirmwareOperating system · Cisco

CVE-2022-20711

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
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 exist in Cisco Small Business RV160, RV260, RV340, and RV345 series routers allowing remote attackers to execute arbitrary code, elevate privileges, execute arbitrary commands, bypass authentication/authorization, fetch and run unsigned software, and cause denial of service.

MitigationApply the latest firmware update provided by Cisco for the affected RV series routers; if no patch is available, consider network segmentation and restricting management interface access to trusted networks.

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
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 the router model
    Access the router's web interface (typically https://192.168.1.1) and navigate to Device or Status pages, or use the CLI command 'show version' to display the hardware model (RV340, RV340w, RV345, or RV345p)
    Affected if The model is one of RV340, RV340w, RV345, or RV345p
  2. Locate the firmware version
    In the router web interface, go to Device or Status pages to view the firmware version, or use the CLI command 'show version' to display the installed firmware build number
    Affected if A firmware version is displayed on the device
  3. Compare firmware version against affected range
    Compare your installed firmware version number to the affected threshold of 1.0.03.24 - versions 1.0.03.24 and below are vulnerable
    Affected if The installed firmware version is 1.0.03.24 or lower (for example, 1.0.03.22, 1.0.02.15, etc.)
  4. Assess exposure of management interface
    Determine if the router management interface (web UI or CLI) is accessible from untrusted networks or the internet, or check firewall rules that allow external access to ports 443 or 80 on the router
    Affected if The router management interface is reachable from untrusted networks or directly exposed to the internet

The environment is affected if the router model is an RV340, RV340w, RV345, or RV345p running firmware version 1.0.03.24 or lower, and the management interface is accessible to potential attackers.

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 the latest firmware update provided by Cisco for the affected RV series routers; if no patch is available, consider network segmentation and restricting management interface access to trusted networks.

Fix this in Rv340 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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-20711 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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