Rv340 FirmwareOperating system · Cisco
CVE-2022-20708
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 Cisco Small Business RV160, RV260, RV340, and RV345 Series Routers could allow an attacker to do any of the following: Execute arbitrary code Elevate privileges Execute arbitrary commands Bypass authentication and authorization protections Fetch and run unsigned software Cause denial of service (DoS) 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 exist in the firmware of Cisco Small Business RV series routers (RV160, RV260, RV340, RV345) allowing remote attackers to execute arbitrary code/commands, escalate privileges, bypass authentication, and cause denial of service. The vulnerabilities stem from insufficient input validation and authentication enforcement in the web management interface.
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
<= 1.0.03.24
Rv340w FirmwareOperating system
<= 1.0.03.24
Rv345 FirmwareOperating system
<= 1.0.03.24
Rv345p FirmwareOperating system
<= 1.0.03.24CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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 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 one of RV340, RV340w, RV345, or RV345p and the firmware version is at or below 1.0.03.24
-
Check the installed firmware versionAccess the router's web interface, navigate to the Administration or Status page, and locate the firmware version field. Alternatively, use the CLI command 'show version' if SSH/Telnet access is available.Affected if The displayed firmware version is 1.0.03.24 or any earlier version (e.g., 1.0.03.20, 1.0.02.15)
-
Compare version against affected rangeCompare your recorded firmware version number to the affected range: any version less than or equal to 1.0.03.24 is considered vulnerableAffected if The firmware version is <= 1.0.03.24 (for example: 1.0.03.22, 1.0.03.18, 1.0.02.10)
A user is affected if their Cisco RV340, RV340w, RV345, or RV345p router runs firmware version 1.0.03.24 or any earlier version.
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.
From vendor dataApply the vendor-supplied firmware patches from Cisco's security advisory immediately; restrict management interface access to trusted networks and monitor for indicators of compromise.
Fix this in Rv340 Firmware
Exploited in the wild — priority engagement
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20708 — 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-2022-20708 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