Rv340 FirmwareOperating system · Cisco
CVE-2022-20702
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 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 confidenceMultiple vulnerabilities in Cisco Small Business RV160, RV260, RV340, and RV345 Series Routers could allow an attacker to execute arbitrary code, elevate privileges, execute arbitrary commands, bypass authentication and authorization protections, fetch and run unsigned software, or cause denial of service. The CVSS 7.2 score indicates high-severity issues requiring urgent attention.
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.24
Rv340w FirmwareOperating system
<= 1.0.03.24
Rv345 FirmwareOperating system
<= 1.0.03.24
Rv345p FirmwareOperating system
<= 1.0.03.24
Rv160 FirmwareOperating system
<= 1.0.01.05
Rv160w FirmwareOperating system
<= 1.0.01.05
Rv260 FirmwareOperating system
<= 1.0.01.05
Rv260p FirmwareOperating system
<= 1.0.01.05CVSS 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 router physically or access its web interface. The model number (RV160, RV260, RV340, RV345, or their variants with 'w' or 'p' suffixes) is printed on the device label or displayed in the dashboard.Affected if The router model is one of: RV160, RV160w, RV260, RV260p, RV340, RV340w, RV345, or RV345p.
-
Determine the installed firmware versionAccess the router web interface and navigate to Administration > Firmware Upgrade or use the CLI command 'show version' to retrieve the current firmware version number.Affected if The firmware version cannot be determined or is not visible in the router interface.
-
Compare firmware version to affected rangesCompare the installed firmware version against the affected version thresholds. For RV340/RV340w/RV345/RV345p models, the affected version is 1.0.03.24 or lower. For RV160/RV160w/RV260/RV260p models, the affected version is 1.0.01.05 or lower.Affected if The installed firmware version is at or below 1.0.03.24 for RV340/RV340w/RV345/RV345p models, or at or below 1.0.01.05 for RV160/RV160w/RV260/RV260p models.
-
Check if remote management is enabledAccess the router web interface and navigate to VPN > Remote Management or Administration > Remote Management to verify whether remote management access is enabled. Also check firewall rules that may permit external access to the router management interface.Affected if Remote management is enabled and the router is accessible from untrusted networks.
-
Verify network exposureDetermine if the router management interface (HTTP/HTTPS on ports 80/443 or other management ports) is reachable from the internet by reviewing port forwarding rules, WAN interface accessibility, or using external port scanning tools.Affected if The router management interface is directly exposed to the internet or reachable from untrusted networks.
A user is affected if they own an RV160, RV260, RV340, or RV345 series router (or their variants) running firmware at or below the affected version thresholds and the router is accessible to potential attackers.
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 · scopedApply Cisco-provided firmware updates for the affected RV series routers as soon as they become available, and review Cisco security advisory for specific vulnerability details and remediation steps.
Latest firmware version beyond 1.0.03.24 for RV340/RV345 series or beyond 1.0.01.05 for RV160/RV260 series (check Cisco advisory for exact fixed version)
- 1. Navigate to the Cisco Software Download page for Small Business RV series routers
- 2. Locate the specific router model (RV160, RV260, RV340, or RV345 series)
- 3. Download the latest available firmware version for your router model
- 4. Access the router's web-based management interface
- 5. Navigate to the Administration or System Upgrade section
- 6. Upload and install the new firmware version
- 7. After upgrade, verify the firmware version matches the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Rv340 Firmware
Scoped from the published advisory
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20702 — 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-20702 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