CVE-2021-1610
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 vulnerabilities in the web-based management interface of Cisco Small Business RV340, RV340W, RV345, and RV345P routers allow unauthenticated or authenticated attackers to execute arbitrary code, cause denial of service, or execute 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 modelLocate the model number on the physical device label or check the web-based management interface dashboard for the exact model (RV340, RV340W, RV345, or RV345P)Affected if Router model is one of RV340, RV340W, RV345, or RV345P and firmware version is below 1.0.03.22
-
Check firmware versionLog into the web-based management interface, navigate to the Status or System Summary page, and locate the firmware version field. Alternatively, use the CLI command 'show version' and look for the firmware revision number.Affected if Firmware version is lower than 1.0.03.22 (for example, 1.0.03.20, 1.0.02.15, etc.)
-
Verify web-based management is enabledIn the web-based management interface, go to Firewall > Access Rules or Administration > Management Access, and check if HTTP or HTTPS management access is enabled on any WAN interface.Affected if Web-based management interface is enabled and accessible from WAN (or untrusted networks)
-
Check management interface exposureFrom the router CLI or web interface, review the access rules or firewall settings to determine if the management interface (HTTP/HTTPS on ports 80/443) is exposed to the internet or untrusted networks.Affected if The management interface is reachable from external IP addresses or WAN-facing interfaces
You are affected if you own an RV340, RV340W, RV345, or RV345P router running firmware version earlier than 1.0.03.22 with web-based management enabled and exposed.
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 Cisco's available firmware updates for the RV series routers. If patches are unavailable, restrict web-based management interface access to trusted networks or disable it entirely until updates can be applied.
Firmware version 1.0.03.22 or later for RV340/RV340W/RV345/RV345P
- 1. Visit the Cisco Software Download page for Small Business RV340 Series routers at cisco.com
- 2. Locate the firmware download section for your specific model (RV340, RV340W, RV345, or RV345P)
- 3. Download firmware version 1.0.03.22 or later
- 4. Access the router's web-based management interface
- 5. Navigate to the Administration or System Management section
- 6. Select the firmware upgrade option
- 7. Upload the downloaded firmware file
- 8. Wait for the upgrade process to complete and the router to reboot
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1610 — 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-1610 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