dbcve.org
Rv340 FirmwareOperating system · Cisco

CVE-2023-20073

CRITICAL · 9.8 CVSS v3.1 Published 2023-04-05
Fix available
A fix is available. Upgrade to after 1.0.03.29 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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
A vulnerability in the web-based management interface of Cisco RV340, RV340W, RV345, and RV345P Dual WAN Gigabit VPN Routers could allow an unauthenticated, remote attacker to upload arbitrary files to an affected device. This vulnerability is due to insufficient authorization enforcement mechanisms in the context of file uploads. An attacker could exploit this vulnerability by sending a crafted HTTP request to an affected device. A successful exploit could allow the attacker to upload arbitrary files to 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 confidence

Unauthenticated remote file upload vulnerability in Cisco RV340/RV340W/RV345/RV345P VPN router web management interface. Attackers can craft HTTP requests to bypass authorization and upload arbitrary files to affected devices due to insufficient validation in the file upload mechanism.

MitigationApply Cisco firmware updates when available. Restrict web-based management interface access to trusted internal networks or disable remote management if not required.

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
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 the device model
    Check the product label or access the device status page to confirm the exact model number (RV340, RV340W, RV345, or RV345P)
    Affected if The device is any of these four models and the firmware version is at or below 1.0.03.29
  2. Determine the installed firmware version
    Log into the web management interface and navigate to the status or system summary page to view the current firmware version, or use the CLI command 'show version' if SSH access is available
    Affected if The firmware version displayed is 1.0.03.29 or any version lower than that number
  3. Verify if the web-based management interface is accessible
    Attempt to reach the device IP address on HTTP/HTTPS ports from the network segment you are checking; confirm the management login page loads
    Affected if The web management interface is reachable from a network where untrusted users could send HTTP requests to the device
  4. Check if remote management is enabled
    In the web interface, navigate to the Administration or System Setup section and locate the remote management settings to see if remote access via HTTP/HTTPS is permitted
    Affected if Remote management is enabled and allows access from outside trusted internal networks

The environment is affected if the device is a Cisco RV340, RV340W, RV345, or RV345P running firmware version 1.0.03.29 or lower, and the web management interface is accessible 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 a release after 1.0.03.29
Interim mitigation

Apply Cisco firmware updates when available. Restrict web-based management interface access to trusted internal networks or disable remote management if not required.

Recommended fix Moderate confidence

Cisco RV340/RV340W/RV345/RV345P firmware >= 1.0.03.30

  1. 1. Navigate to the Cisco Software Download page for RV340, RV340W, RV345, and RV345P routers
  2. 2. Locate the firmware downloads section
  3. 3. Download firmware version 1.0.03.30 or later (the first fixed release addressing this vulnerability)
  4. 4. Access the router's web-based management interface
  5. 5. Navigate to the Administration > Firmware Upgrade section
  6. 6. Upload and apply the new firmware version
  7. 7. Wait for the device to reboot and verify the upgrade was successful
  8. 8. Confirm the new firmware version is 1.0.03.30 or later
Caveat Review Cisco release notes for any configuration or feature changes between your current version and the upgrade version before applying

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
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,590
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,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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