Rv340 Dual Wan Gigabit Vpn Router FirmwareOperating system · Cisco
CVE-2020-3357
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 · uneditedA vulnerability in the Secure Sockets Layer (SSL) VPN feature of Cisco Small Business RV340, RV340W, RV345, and RV345P Dual WAN Gigabit VPN Routers could allow an unauthenticated, remote attacker to execute arbitrary code on an affected device or cause the device to reload, resulting in a denial of service (DoS) condition. The vulnerability exists because HTTP requests are not properly validated. An attacker could exploit this vulnerability by sending a crafted HTTP request over an SSL connection to an affected device. A successful exploit could allow the attacker to remotely execute arbitrary code on the device or cause the device to reload, 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 confidenceA critical vulnerability exists in the SSL VPN feature of Cisco Small Business RV340/RV345 series routers where HTTP requests are not properly validated before processing. This allows unauthenticated remote attackers to send specially crafted HTTP requests over SSL that can result in arbitrary code execution on the device or cause a denial of service via device reload.
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 Dual Wan Gigabit Vpn Router FirmwareOperating system
< 1.0.03.18
Rv340w Dual Wan Gigabit Wireless Ac Vpn Router FirmwareOperating system
< 1.0.03.18
Rv345 Dual Wan Gigabit Vpn Router FirmwareOperating system
< 1.0.03.18
Rv345p Dual Wan Gigabit Poe Vpn Router FirmwareOperating system
< 1.0.03.18CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the router modelLog into the router web interface or check the physical device label to confirm the exact model (RV340, RV340w, RV345, or RV345p).Affected if The model is not one of these four: RV340, RV340w, RV345, or RV345p.
-
Check the firmware versionLog into the router web interface, navigate to Administration > Firmware Update, or use the CLI command 'show version' to determine the installed firmware version.Affected if The firmware version is lower than 1.0.03.18.
-
Verify SSL VPN is enabledLog into the router web interface and navigate to VPN > SSL VPN, or use the CLI command 'show sslvpn config' to check if the SSL VPN feature is currently active.Affected if SSL VPN is enabled and the firmware version is below 1.0.03.18.
-
Review SSL VPN configuration settingsIn the SSL VPN settings page, check the interface binding (which WAN interface(s) SSL VPN is bound to) and whether any IP access restrictions are configured.Affected if SSL VPN is bound to a WAN interface without IP access restrictions.
The device is affected if it is an RV340, RV340w, RV345, or RV345p model running firmware version below 1.0.03.18 with SSL VPN feature enabled.
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.18
Apply the vendor firmware update from Cisco when available. Until then, disable the SSL VPN feature if not required, implement network access controls to limit VPN exposure to trusted IPs only, and consider network segmentation to isolate affected devices.
Firmware version 1.0.03.18 or later for RV340/RV340W/RV345/RV345P
- 1. Download the firmware version 1.0.03.18 or later for your specific model (RV340, RV340W, RV345, or RV345P) from the Cisco website
- 2. Access the Cisco Small Business RV series router web management interface
- 3. Navigate to the Administration menu or System Settings
- 4. Locate the Firmware Upgrade or Software Update section
- 5. Upload the downloaded firmware file (.bin) to the router
- 6. Wait for the firmware upload to complete - do not power off the device during this process
- 7. The router will automatically reboot after the upgrade completes
- 8. Verify the firmware version has been updated to 1.0.03.18 or later in the router's status page
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Rv340 Dual Wan Gigabit Vpn Router Firmware
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3357 — 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-2020-3357 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