dbcve.org
Rv340 FirmwareOperating system · Cisco

CVE-2023-20007

HIGH · 7.2 CVSS v3.1 Published 2023-01-20
Fix available
A fix is available. Upgrade to 1.0.03.29 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
A vulnerability in the web-based management interface of Cisco Small Business RV340, RV340W, RV345, and RV345P Dual WAN Gigabit VPN Routers could allow an authenticated, remote attacker to execute arbitrary code or cause the web-based management process on the device to restart unexpectedly, resulting in a denial of service (DoS) condition. The attacker must have valid administrator credentials. This vulnerability is due to insufficient validation of user-supplied input to the web-based management interface. An attacker could exploit this vulnerability by sending crafted HTTP input to an affected device. A successful exploit could allow the attacker to execute arbitrary code as the root user on the underlying operating system or cause the web-based management process to restart, resulting in a DoS condition.

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 confidence

This is an input validation vulnerability in the web-based management interface of Cisco Small Business RV340/RV340W/RV345/RV345P VPN routers. An authenticated attacker with administrator credentials can send crafted HTTP requests to inject and execute arbitrary code as root user on the underlying operating system, or cause the web management process to crash resulting in denial of service.

MitigationApply the Cisco firmware update when available; in the interim, restrict web-based management interface access to trusted internal networks or IPs only to reduce 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.29
Rv340w FirmwareOperating system
Affected:< 1.0.03.29
Rv345 FirmwareOperating system
Affected:< 1.0.03.29
Rv345p FirmwareOperating system
Affected:< 1.0.03.29

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 web-based management interface or use CLI command 'show version' to confirm the device is one of: RV340, RV340W, RV345, or RV345P
    Affected if Device model is RV340, RV340W, RV345, or RV345P
  2. Check firmware version
    In the web interface, navigate to Status > System Summary or use CLI command 'show version' to display the firmware version. Compare against 1.0.03.29
    Affected if Firmware version is lower than 1.0.03.29 (e.g., 1.0.03.28, 1.0.03.26, etc.)
  3. Verify web-based management is enabled
    In the web interface, go to Administration > Management Interface or check via CLI with 'show web-management' to confirm HTTP/HTTPS management is enabled
    Affected if Web-based management interface is enabled and accessible
  4. Check management interface access restrictions
    In the web interface, navigate to Administration > Management Interface > Access Rules to review which IP addresses or networks are permitted to access the web management
    Affected if Web management is accessible from untrusted or external networks (0.0.0.0/0 or wide IP ranges)

The device is affected if it is an RV340/RV340W/RV345/RV345P router running firmware version lower than 1.0.03.29 and the web-based management interface is enabled and accessible.

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.29 or later
Fixed in 1.0.03.29
Interim mitigation

Apply the Cisco firmware update when available; in the interim, restrict web-based management interface access to trusted internal networks or IPs only to reduce attack surface.

Recommended fix High confidence

Firmware version 1.0.03.29 or later for RV340, RV340W, RV345, and RV345P

  1. 1. Download the fixed firmware version 1.0.03.29 or later from the Cisco software download center (software.cisco.com) for your specific model (RV340, RV340W, RV345, or RV345P)
  2. 2. Log in to the web-based management interface of the affected router using valid administrator credentials
  3. 3. Navigate to Administration > Firmware Upgrade (or similar firmware update section in the web UI)
  4. 4. Click the firmware upload option and select the downloaded firmware file (.bin)
  5. 5. Confirm the upgrade and wait for the upload to complete - do not power off the device during this process
  6. 6. The router will automatically reboot after the firmware is applied
  7. 7. After reboot, verify the firmware version in the web UI to confirm the upgrade was successful (should show 1.0.03.29 or later)
  8. 8. Reconfigure any settings if they were reset to factory defaults after the upgrade
Caveat Review release notes for any configuration changes or migration requirements between versions; backup current configuration before upgrading

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

Fix this in Rv340 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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