Rv340 FirmwareOperating system · Cisco
CVE-2022-20753
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 web-based management interface of Cisco Small Business RV340 and RV345 Routers could allow an authenticated, remote attacker to execute arbitrary code on an affected device. This vulnerability is due to insufficient validation of user-supplied input. An attacker could exploit this vulnerability by sending malicious input to an affected device. A successful exploit could allow the attacker to execute remote code on the affected device. To exploit this vulnerability, an attacker would need to have valid Administrator credentials on 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 confidenceThe vulnerability is a code injection flaw in the web-based management interface of Cisco RV340 and RV345 routers. Insufficient validation of user-supplied input allows an authenticated attacker with Administrator credentials to inject and execute arbitrary code on the affected device.
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.27
Rv340w FirmwareOperating system
< 1.0.03.27
Rv345 FirmwareOperating system
< 1.0.03.27
Rv345p FirmwareOperating system
< 1.0.03.27CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 device label or access the web-based management interface and check the Status or Dashboard page for the hardware model (RV340, RV340w, RV345, or RV345p)Affected if Model is one of RV340, RV340w, RV345, or RV345p
-
Check firmware versionIn the web-based management interface, navigate to Status or System section and locate the Firmware version field. Compare the installed version to the affected range: vulnerable if version is earlier than 1.0.03.27Affected if Firmware version is less than 1.0.03.27
-
Confirm web-based management is enabledIn the web-based management interface, go to Administration, Management, or Security settings and verify whether the HTTP or HTTPS web management interface is enabledAffected if Web-based management interface is enabled and accessible
-
Check remote access settingsIn the web-based management interface under Administration, Management Access, or Remote Management settings, determine whether web management is accessible from WAN (remote) networks or only from LANAffected if Remote (WAN) access to the web management interface is permitted
Your environment is affected if you are running a Cisco RV340, RV340w, RV345, or RV345p router with firmware version earlier than 1.0.03.27 and the web-based management interface is enabled, especially if accessible remotely.
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.27
Apply the Cisco firmware update for RV340/RV345 routers. If patches are unavailable, restrict web management interface access to trusted networks or disable remote management entirely.
RV340/RV340w/RV345/RV345p Firmware version 1.0.03.27 or later
- Access the Cisco Small Business RV340/RV345 router web-based management interface
- Navigate to the Administration or Firmware Upgrade section
- Locate the firmware update option
- Upload and install firmware version 1.0.03.27 or later
- Verify the firmware was successfully installed by checking the firmware version in the device status
- Reboot the router if not automatically prompted
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Rv340 Firmware
Scoped from the published advisory
- Consultation4.0 h
- Implementation3.0 h
- Testing4.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,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20753 — 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-20753 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