CVE-2021-1609
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 the web-based management interface of the Cisco Small Business RV340, RV340W, RV345, and RV345P Dual WAN Gigabit VPN Routers could allow an attacker to do the following: Execute arbitrary code Cause a denial of service (DoS) condition Execute arbitrary commands 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 critical vulnerabilities in the web-based management interface of Cisco Small Business RV340, RV340W, RV345, and RV345P VPN routers allow remote attackers to execute arbitrary code, cause denial of service, or run arbitrary commands on the affected devices.
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< 1.0.03.22CVSS 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 router modelAccess the device web UI or CLI and confirm the model is RV340, RV340W, RV345, or RV345PAffected if Model is one of these four models and the web management interface is accessible
-
Check firmware versionNavigate to the web UI Status page or use 'show version' command via CLI to retrieve the firmware versionAffected if Firmware version is lower than 1.0.03.22 (for example, 1.0.03.20, 1.0.02.15, etc.)
-
Verify web management interface statusGo to Administration > Web Management in the router UI or check via CLI for service statusAffected if Web-based management interface is enabled and accessible from WAN or untrusted networks
-
Check remote access configurationReview the Access Control settings under Administration to see if web management is restricted to specific IP addresses or if it allows external accessAffected if Web management is accessible from any remote IP address (0.0.0.0/0) or from WAN interface without ACL restrictions
The device is affected if it is an RV340, RV340W, RV345, or RV345P router running firmware version prior to 1.0.03.22 with the web-based management interface enabled and accessible.
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.22
Apply the Cisco firmware update for these models when released; in the interim, disable remote web management access or restrict it to trusted IP addresses via ACLs.
Firmware version 1.0.03.22 or later for Cisco Small Business RV340/RV340W/RV345/RV345P routers
- 1. Identify the current firmware version by logging into the router web interface and navigating to Administration > Firmware Upgrade, or by checking the status page
- 2. Download the firmware version 1.0.03.22 or later from the Cisco software download center (tools.cisco.com) for your specific router model (RV340, RV340W, RV345, or RV345P)
- 3. Access the router's web-based management interface and navigate to Administration > Firmware Upgrade
- 4. Click the firmware upload button and select the downloaded firmware file (.img or .bin)
- 5. Wait for the upload to complete - do not power off the router during this process
- 6. The router will automatically reboot after the firmware is applied
- 7. After reboot, verify the new firmware version is showing as 1.0.03.22 or later in the router status
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2021-1609 — 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-2021-1609 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