dbcve.org
Rv340 FirmwareOperating system · Cisco

CVE-2022-20801

HIGH · 7.2 CVSS v3.1 Published 2022-05-04
Fix available
A fix is available. Upgrade to 1.0.03.27 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 the web-based management interface of Cisco Small Business RV340 and RV345 Routers could allow an authenticated, remote attacker to inject and execute arbitrary commands on the underlying operating system of an affected device. These vulnerabilities are due to insufficient validation of user-supplied input. An attacker could exploit these vulnerabilities by sending malicious input to an affected device. A successful exploit could allow the attacker to execute arbitrary commands on the underlying Linux operating system of the affected device. To exploit these vulnerabilities, an attacker would need to have valid Administrator credentials on the affected device.

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 command injection vulnerabilities exist in the web-based management interface of Cisco Small Business RV340 and RV345 Routers. Due to insufficient validation of user-supplied input, an authenticated attacker with Administrator credentials can inject and execute arbitrary Linux commands on the affected device.

MitigationApply Cisco's available firmware updates for RV340/RV345 routers. If no update is available, restrict administrative access to trusted IP addresses only and monitor for unauthorized administrative sessions.

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.27
Rv340w FirmwareOperating system
Affected:< 1.0.03.27
Rv345 FirmwareOperating system
Affected:< 1.0.03.27
Rv345p FirmwareOperating system
Affected:< 1.0.03.27

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

CVSS:3.1/AV:N/AC:L/PR:H/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
    Access the router's web interface status page, check the physical device label, or use the CLI command 'show version' to determine the exact model number
    Affected if The model is RV340, RV340w, RV345, or RV345p
  2. Check firmware version
    In the web interface, navigate to Administration > Firmware Upgrade or Status page to view the installed firmware version. Alternatively, use CLI 'show version' to display the firmware version
    Affected if The firmware version is below 1.0.03.27 (for example, 1.0.03.26 or earlier)
  3. Confirm web-based management is enabled
    In the router web interface, go to Administration > Management Access and verify if HTTP or HTTPS web management is enabled
    Affected if HTTP or HTTPS web management interface is enabled and accessible
  4. Review administrative access logs
    In the router web interface, navigate to Administration > Logs or System Logs to examine recent administrative login events for unexpected sessions
    Affected if There are administrative sessions from unexpected IP addresses or at times you do not recognize

The environment is affected if the device is an RV340, RV340w, RV345, or RV345p router running firmware version 1.0.03.26 or earlier with the web-based management interface enabled.

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.03.27 or later
Fixed in 1.0.03.27
Interim mitigation

Apply Cisco's available firmware updates for RV340/RV345 routers. If no update is available, restrict administrative access to trusted IP addresses only and monitor for unauthorized administrative sessions.

Recommended fix High confidence

1.0.03.27

  1. Download the firmware version 1.0.03.27 (or later) from Cisco's official support website for your specific model (RV340, RV340w, RV345, or RV345p)
  2. Log in to the router's web-based management interface with Administrator credentials
  3. Navigate to the Administration or System Management section
  4. Locate the Firmware Upgrade option
  5. Upload and apply the downloaded firmware file
  6. Wait for the router to complete the upgrade process and reboot automatically
  7. Verify the firmware version has been updated to 1.0.03.27 or later in the device status
Caveat Firmware upgrade may cause brief service interruption; ensure configuration is backed up before upgrading

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

Fix this in Rv340 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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