Rv340 FirmwareOperating system · Cisco
CVE-2022-20799
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 · uneditedMultiple 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 · high confidenceMultiple command injection vulnerabilities in the web-based management interface of Cisco Small Business RV340 and RV345 routers allow an authenticated remote attacker with Administrator credentials to execute arbitrary Linux commands due to insufficient validation of user-supplied input in the management interface.
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
< 1.0.03.27
Rv340w FirmwareOperating system
< 1.0.03.27
Rv345 FirmwareOperating system
< 1.0.03.27
Rv345p FirmwareOperating system
< 1.0.03.27CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the router modelLocate the model number on the router physical label or access the administration interface to confirm whether the device is an RV340, RV340w, RV345, or RV345p model.Affected if The device is any of these models.
-
Determine the installed firmware versionAccess the web-based management interface and navigate to the Administration or Status section to view the current firmware version. Alternatively, use the CLI command 'show version' if SSH or console access is available.Affected if The firmware version is below 1.0.03.27.
-
Verify if web-based management interface is enabledIn the router administration panel, check the management access settings under Administration > Remote Management to confirm whether the HTTP/HTTPS web interface is enabled for LAN or WAN access.Affected if The web-based management interface is enabled.
-
Check administrative user accountsReview the list of configured administrator accounts in the router management interface under Administration > User Accounts to determine if administrator-level accounts exist.Affected if Any administrator accounts are configured and accessible.
The environment is affected if the router model is RV340, RV340w, RV345, or RV345p, the installed firmware version is earlier than 1.0.03.27, and the web-based management interface is enabled with administrator accounts present.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.0.03.27
Apply the relevant Cisco firmware update for RV340/RV345 routers once available; restrict administrative access to trusted networks and enforce strong credential policies to reduce attack surface.
Cisco RV340/RV345 Firmware 1.0.03.27 or later
- 1. Identify current firmware version by logging into the router's web-based management interface and navigating to Device Overview or Status page
- 2. Navigate to Cisco's official software download page for RV340/RV345 series routers at tools.cisco.com
- 3. Download firmware version 1.0.03.27 or later for your specific model (RV340, RV340w, RV345, or RV345p)
- 4. Log into the router's web management interface with Administrator credentials
- 5. Navigate to Administration > Firmware Upgrade or similar section depending on the UI
- 6. Upload the downloaded firmware file and initiate the upgrade process
- 7. Wait for the upgrade to complete and the router to reboot automatically
- 8. After reboot, verify the firmware version has been updated to 1.0.03.27 or later in the Device Overview
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
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20799 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-20799 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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