Rv340 FirmwareOperating system · Cisco
CVE-2021-1414
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 Cisco RV340, RV340W, RV345, and RV345P Dual WAN Gigabit VPN Routers could allow an authenticated, remote attacker to execute arbitrary code with elevated privileges equivalent to the web service process on an affected device. These vulnerabilities exist because HTTP requests are not properly validated. An attacker could exploit these vulnerabilities by sending a crafted HTTP request to the web-based management interface of an affected device. A successful exploit could allow the attacker to remotely execute arbitrary code on the 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 confidenceVulnerability in Cisco RV340/RV340W/RV345/RV345P VPN routers allows authenticated remote attackers to execute arbitrary code via crafted HTTP requests to the web management interface due to improper input validation. The attacker gains privileges equivalent to the web service process.
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.21
Rv340w FirmwareOperating system
< 1.0.03.21
Rv345 FirmwareOperating system
< 1.0.03.21
Rv345p FirmwareOperating system
< 1.0.03.21CVSS 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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 modelLog into the router web interface or check the physical device label to confirm the model is one of: RV340, RV340W, RV345, or RV345PAffected if Model is not one of these four listed models - this CVE does not apply
-
Check installed firmware versionIn the router web interface, navigate to Status > System Summary or similar firmware/version information page. Compare the displayed firmware version against 1.0.03.21Affected if Firmware version is lower than 1.0.03.21 (for example, 1.0.03.20, 1.0.02.15, etc.)
-
Verify web management interface is accessibleAttempt to access the router web interface via HTTP or HTTPS from a remote system, or check the Administration > Web Management settings to confirm the interface is enabled and accessibleAffected if Web management interface is enabled and reachable from a network where attackers could send HTTP requests
-
Check if remote access is allowed for web managementIn the router web interface, examine Administration > Remote Management or similar settings to determine if remote HTTP/HTTPS access is permittedAffected if Remote management via HTTP/HTTPS is enabled, allowing unauthenticated (to the attacker) network access to the web interface
The router is affected if it is an RV340, RV340W, RV345, or RV345P model running firmware version lower than 1.0.03.21 AND the web management interface is accessible to attackers.
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 data1.0.03.21
Apply the vendor-supplied firmware update from Cisco to patch the input validation vulnerabilities in the web-based management interface.
Fix this in Rv340 Firmware
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1414 — 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-1414 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