dbcve.org
Rv340 FirmwareOperating system · Cisco

CVE-2022-20842

CRITICAL · 9.8 CVSS v3.1 Published 2022-08-10
Fix available
A fix is available. Upgrade to 1.0.03.28 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 unauthenticated, remote attacker to execute arbitrary code or cause a denial of service (DoS) condition on an affected device. 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 in Cisco Small Business RV160, RV260, RV340, and RV345 Series Routers allow unauthenticated remote attackers to execute arbitrary code or cause denial of service without authentication.

MitigationApply Cisco firmware updates when available; until then, restrict management interface exposure to trusted networks or implement strict ACLs to limit attack surface.

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

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 router model
    Access router web interface (typically at 192.168.1.1) or CLI and note the exact model number from the device label or status page
    Affected if Model is RV340, RV340w, RV345, or RV345p (or RV160/RV260 if also in use)
  2. Check firmware version
    In web interface go to Status > System Summary; or in CLI run 'show version' and locate the firmware version string
    Affected if Firmware version is lower than 1.0.03.28 (for example 1.0.03.20, 1.0.03.15, etc.)
  3. Determine if management interface is WAN-accessible
    In web interface navigate to Firewall > Access Rules or WAN > General. Check if HTTP/HTTPS management is allowed on WAN interface or if external IP binding is enabled
    Affected if Management interface (HTTP/HTTPS on WAN or external IP) is accessible from untrusted networks

Affected if the router is an RV340/RV340w/RV345/RV345p model running firmware version below 1.0.03.28 AND the 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 1.0.03.28 or later
Fixed in 1.0.03.28
Interim mitigation

Apply Cisco firmware updates when available; until then, restrict management interface exposure to trusted networks or implement strict ACLs to limit attack surface.

Recommended fix High confidence

Firmware 1.0.03.28 for RV340/RV340w/RV345/Rv345p

  1. 1. Identify the exact Cisco Small Business router model (RV340, RV340w, RV345, or RV345p) from the device label or web interface.
  2. 2. Navigate to the Cisco Software Downloads page and locate the firmware download section for your specific router model.
  3. 3. Download firmware version 1.0.03.28 or later for your router model.
  4. 4. Access the router's web-based management interface by entering the device's IP address in a browser.
  5. 5. Navigate to the Administration > Firmware Upgrade or similar section in the web interface.
  6. 6. Click the option to upload or browse for the new firmware file you downloaded.
  7. 7. Wait for the firmware upload to complete - do not power off the device during this process.
  8. 8. The router will automatically reboot after the firmware is applied.

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

Fix this in Rv340 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
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,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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